Normal view
Web Designers Love Dark Mode Toggles. Users Might Not Care.
Today, WordPress Ended a 16-Year Tradition… Meet Ipsum!
-
Website and Communications Blog
- What I learned in my summer internship researching digital content accessibility
What I learned in my summer internship researching digital content accessibility
In this post, User Experience team intern Hannah Watson shares her work over the summer researching digital content accessibility with the EdWeb 2 publishing community.
Introduction
As part of my internship with the User Experience Service, I have been investigating digital accessibility at the content level across University web pages, particularly on EdWeb 2 sites. Digital accessibility at the content level is about applying principles of accessibility to how web content is written and formatted. This includes, but is not limited to, content features such as heading levels, links, and alt text. It does not include anything that is not involved with content design or that is controlled at a higher level by the Content Management System (CMS), such as font, font size, or colour contrast.
Research aims and scope
The specific research questions for this project were:
- How do web publishers learn about digital content accessibility?
- What do web publishers know about digital content accessibility?
- How do web publishers implement digital accessibility requirements and principles in their content?
- What challenges do web publishers face in creating digitally accessible content?
More comprehensively, I was investigating the accessibility of:
- Heading levels
- Ensuring that heading levels are used correctly
- Not using heading levels for emphasis
- Links
- Clear and concise link text which describes the linked destination
- Link text which makes sense on its own
- Avoiding URLs on web pages
- Lists
- Alt text
- Clear link text that describes the image
- Images
- Ensuring that all images have appropriate alt text
- Avoiding images of text
- Videos
- Including human-corrected captions with any videos uploaded to web pages
- Making sure that transcripts are available for all videos uploaded to web pages
- Italic, bold, and underlined text
For more detailed guidance on these topics, please refer to the University of Edinburgh editorial style guide.
Editorial style guide | Information Services
This research has been necessary for the User Experience team as it allows us to identify which areas of content accessibility are challenging for web publishers. From this, the team can adapt guidance and training to provide extra support on these more challenging areas where possible.
Research methods
Interviews with web publishers
I started my research by setting up short, informal interviews with six University web publishers. In these interviews, I asked the publishers about their experiences of creating digitally accessible content. The aim of these conversations was to understand how publishers learned about digital accessibility and what challenges they face when making content as accessible as it can be. During the interviews, we referred to web pages that these publishers work on to get concrete examples that illustrate the topics we discussed. Through these interviews, I was able to identify a number of trends, particularly in the challenges that the interviewees and their colleagues face.
Survey of EdWeb 2 publishers and the Web Accessibility Special Interest Group
Following these interviews, I created a survey to further investigate the findings and collate more supporting evidence for these findings. The survey consisted of 10 questions, three of which were demographic based as a filter, with a final question asking permission to follow up with those who responded.
The other six questions asked about:
- which actions the participants took to make their content digitally accessible
- what resources they used to do so
- what challenges they face in doing so
The findings from the survey were effective in making the information gathered in interviews more robust and provided further evidence for some trends that were identified previously.
To publicise this survey, I sent a brief statement explaining my research into two Teams channels, the Web Accessibility Special Interest Group and the EdWeb 2 Community. Overall, the survey received five responses, and while this is a limited number, I found that it helped to support the findings from the interviews.
Analysis of Effective Digital Content workbooks
The final method of research that I used to learn about the digital accessibility of content on University web pages was by looking at pages that were submitted within Effective Digital Content workbooks as part of the course. The course requires learners to choose pages from a University website and assess the effectiveness of the content. By looking at the pages that learners selected, I was able to use active examples and make note of content accessibility issues that were present on live pages. This process also highlighted a number of trends.
This method of research was also useful in that it provided two separate sources of data. Firstly, the answers in the workbook helped me to gauge learners’ understanding of the principles covered in the course. Secondly, the web pages linked by those taking the course allowed me to have live examples of content to assess against content accessibility principles. While there was not necessarily overlap between the answers in the workbook and the pages submitted as part of the workbook (as some people may not have been fully or at all responsible for the content on those pages, or the content could have been updated since the workbook was submitted), it was useful to see these things separately.
Findings about accessibility
Combining findings from all areas of research for this project, I have identified a number of trends in the accessibility of digital content.
Headings, alt text, and links are the principles most often put into practice by participants
In the interviews and the survey, participants were asked what principles of accessible digital content they actively used when designing content. More than half of participants mentioned three principles in particular, with all participants mentioning at least two, which were:
- using the correct heading levels
- adding meaningful alt text to an image
- writing clear and descriptive link text
Interestingly, while these principles were mentioned frequently by participants, and evidenced by the websites that we discussed in interviews, they are also principles that are often missed on University web pages. This is discussed in more detail in the corresponding sections further on in this post.
PDFs are hard to avoid
One standout finding from the interviews was that web publishers sometimes struggle to find an effective alternative to PDFs. While PDFs are not necessarily accessible, they do have benefits which make them useful for publishers. For example, they are downloadable, searchable, and cannot be easily edited without permission from the owner. There are ways to make PDFs more accessible, such as avoiding decorative images, adhering to accessible content design principles within the PDF, and checking colour contrast. However, the interviewees were more in favour of finding a way to turn their content into a webpage as this is more likely to result in accessible content.
Out of the survey responses, three also mentioned that they had recently chosen to publish content as a web page rather than as a PDF, highlighting their knowledge that a web page is preferable in terms of accessibility. However, their personal preferences or how difficult they found this is unknown as I was unable to follow up with these participants.
Heading levels are often skipped and headings vague
Across web pages that I assessed for correct heading levels, there were several which skipped heading levels throughout the page content, such as going straight to a heading 3 without that heading being nested within a heading 2 section. Additionally, headings on the University web pages that I investigated were often generic, instead of being specific about what a page or section will contain, which is the recommended approach.
The fact that the web publishers who were interviewed and surveyed were aware of the importance of correct headings levels and specific headings, and that the majority of these publishers have attended a staff training or used the editorial style guide, suggests that the guidance provided is accurate and useful for publishers.
To increase the use of correct heading levels, as well as clear and descriptive headings on web pages, participant responses suggest that increasing the reach and engagement of existing training and resources involving headings would be effective. This includes training provided by the User Experience Service, such as Effective Digital Content or Content Improvement Club, and the University of Edinburgh editorial style guide.
Alt text is well written but sometimes missed
In three of the interviews, and in two survey responses, participants mentioned that they struggled to find the time to add alt text to images on their web pages. However, participants in the interviews also stated that they understood the importance of alt text, and what writing meaningful and clear alt text involves. This is reflected in the answers in Effective Digital Content workbooks. The course contains a question asking learners to write meaningful alt text for two images, and this question is often answered well. This suggests that web publishers understand how to write alt text, and that the obstacle in doing so is more likely to be related to time and resource.
One way that time constraints on adding alt text could be improved is to reduce the number of images on a web page, which will not only make this task more manageable but also is also more sustainable.
Explaining acronyms and abbreviations is common
All five responses to the survey stated that they had explained an acronym or abbreviation recently. Although this did not come up in the interviews often – only once – the survey responses suggest that this is common practice for web publishers who are familiar with digital accessibility principles.
Link text is frequently inline or not descriptive
Participants stated that they understand the importance of clear link text as a principle and make effort to implement this into their content. However, similar to headings, this sentiment is not reflected across numerous University web pages. In some of the pages submitted as part of the Effective Digital Content workbooks that I investigated, there were frequent occurrences of inline link text, or link text that does not clearly describe the linked destination.
To increase the writing of link text on a separate line, as well as clear and descriptive link text, participant responses suggest that increasing the reach and engagement of existing training and resources involving links would be effective. This includes training provided by the User Experience Service, such as Effective Digital Content or Content Improvement Club, and the University of Edinburgh editorial style guide.
Findings about staff experience and engagement
A trend from both the interviews and survey responses is that for many of the people involved with this research, their knowledge of digital accessibility started with a personal interest. Specific examples of this that participants mentioned include learning about accessibility as a student (and then going on to be an accessibility advocate for a student society) and working with disabled students and learning through experience.
During the interviews, multiple staff members mentioned that they believe, through their experiences, that a large part of issues with creating accessible digital content at the University surrounds communication. A combination of factors was discussed that had communication at the centre, including:
- the importance of digital accessibility not being widespread enough.
- consistency about expectations between schools or areas of the University, such as one page being edited by multiple schools or areas and having different standards.
Job-based constraints were also mentioned frequently, such as limited time to add alt text to all images on a web page and working on a page where the lead publisher takes a design forward approach which can sometimes clash with accessible content principles. These answers were also reflected in the survey responses, with all of the responses mentioning either one or both of these problems.
What resources do web publishers use for learning about and developing their digital accessibility skills?
The primary resource that participants mentioned using to learn about digital accessibility and develop their skills was University-provided staff training, with 10 of 11 participants mentioning this. Effective Digital Content was specifically mentioned twice, and Content Improvement Club three times. In the interviews, two participants mentioned more general staff training, with one survey response saying the same. In the survey responses, three participants also said that they used training provided by the Disability Information Team.
The Web Content Accessibility Guidelines 2.2 (WCAG) is another resource that was frequently mentioned by participants, with six in total saying that this is a resource that they use as guidance on accessibility.
The University of Edinburgh editorial style guide was mentioned by five participants as a resource that they used to provide guidance on digital accessibility, in which the guidance reflects what publishers learn in training courses, meaning that information they take from the style guide is in line with accessibility and content design training.
What I learned from researching content accessibility approaches in EdWeb
I learned a lot during my time researching how web publishers at the University of Edinburgh approach creating accessible digital content. I thoroughly enjoyed the opportunity to work with staff from a variety of different areas of the University. This helped me to learn how to identify commonalities in interview and survey responses despite the areas of work being distinct. I also enjoyed this because I was able to learn much more about the work that goes on across the University and what the work of other teams involved.
I also particularly enjoyed the format of my internship being a combination of individual work and working with other members of my team and the Disability Information team. This balance allowed me to set my own goals while still getting the opportunity to work and learn collaboratively as part of a team, prioritising my tasks between my own and those that I was working on with others.
A limitation of my work was that it was much easier to contact and work with staff who have a genuine interest in the subject area of accessibility, which does not lead to research that is representative of how University staff approach digital accessibility as a whole. Having done the research that I have so far, a continuation of the research would be most beneficial if it focused on the experiences and approaches of staff who are less familiar with digital accessibility requirements and principles, as this would create a more well-rounded understanding of web publisher accessibility approaches at the content level.
Furthermore, another limitation of the work was the time constraints which have restricted my ability to develop solutions to issues identified during the research period. This was expected to a degree, as the solutions depended on the outcomes of the research, which has taken the majority of the 12-week period. The positive outcome of this is that the research and findings will provide the User Experience service with information that allows for both further research and for adaptations to guidance and training if it is deemed necessary.
Conclusion
This research has helped the User Experience Service to assess their training and the resources that are available for publishers to learn more about digital content accessibility. Keeping in touch with the publishing community through projects like this helps the team to direct their effort to real challenges that publishers face on a day to day basis.
The research completed throughout the duration of this project will be supported and advanced by further investigation, particularly by communicating with web publishers who are less involved with digital accessibility as a whole. This will likely help in providing more concrete solutions to digital content accessibility issues across EdWeb 2 pages.
Web Registry Development Intern’s September Recap!
I’m Grace, the Web Registry Development Intern for the 2026 Summer! As my internship draws to a close, I discuss how my AI Supported Accessibility Testing, and my Web Estate Dashboard projects have progressed. The first project focused on investigating how AI can be used to automate accessibility testing websites. My second project aimed to produce a dashboard for non-technical audience so they could see their website statistics. I reflect on my project, my experience, and what I’ve learned.
AI Supported Accessibility Testing
Almost three months after I started, my internship is wrapping up. My Summer project aimed to investigate how AI can be used to automate accessibility testing, so we can make sure the web estate is in compliance with Web Content Accessibility Guidelines. Currently, most automated testing (programs like axe DevTools) catches approximately 30% of errors, I aimed to increase that accuracy and investigate where AI can be useful. I’ve learned a lot, but there’s still lots more for me to pick up! The goal was to get AI to test for WCAG violations more accurately, and see if it could be a useful tool in the testing process.
Findings
Rather mundanely, AI won’t be taking over the world anytime soon. AI supported accessibility testing still hovers around 30% accuracy.
Strengths
The agent is good at crawling through sites and identifying suspicious elements that commonly produce issues, things like a pop-up widget or a pdf. It also excels at anything related to markup languages, testing guideline 1.3.5, identify input purpose, for example, which looks to see if input fields are labelled correctly, so computers can autocomplete them. These black-and-white guidelines are easily digestible for AI, it’s when a human aspect in included that AI can stumble.
Weaknesses
In conversations with the accessibility team, it was noted that AI struggles with the “grey-areas” that pop up in the testing process. While the full list of WCAG guidelines is lengthy and specific, the primary goal is to make sites usable for all. A guideline may not explicitly outline why a website fails, but if a human finds it inaccessible, that means it’s inaccessible! An element’s context within a website can drastically change whether or not it’s WCAG compliant, this was something that agents struggled with. I found that agents are too scared to get something wrong to think critically or apply executive judgement.
Aside from that, guidelines that measure things like a logical tab sequence—measuring how intuitive it is for someone to navigate a website with a keyboard—should continue to be tested and reviewed by humans.
Methodology
In the beginning, I did some desk research to find the AI agent best suited for the task at hand. I investigated the different LLMs available through ELM, with varying success. They could analyse whatever screenshots I gave them, but that still required me going through a website and selecting information that was relevant. I pivoted to the ChatGPT software, which was then called Codex. Codex could exit its window and crawl through the site itself autonomously, more closely mimicking how accessibility testing is actually carried out. It was a bit of a learning curve, lots of failed audits that I got to learn from. Throughout the summer, I iterated a master prompt to feed to agents, tinkering away at it bit-by-bit. I made it modular, so it was easy to swap out guidelines based on what you wanted to test. Currently, the prompt sits at 7252 words, and each guideline is split into smaller sections.
![]()
The AI specifications section contributed the most to the wordcount. You have to be very specific about the exact path you want the agent to take. It’s good that you get to have specific control over the testing, less great when you have to soft-parent an agent through pressing the “Tab” key.
This prompt would then produce an audit report, this is distinct from a completed accessibility report. The audit was produced to help a tester identify issues, not to present findings to a wider audience. During my internship, I gave weekly updates to the accessibility team and I was consistently given really valuable feedback that I could integrate back into the master prompt. At the end of my internship, I started scoring the accuracy of the prompt against preexisting human accessibility reports.
Web Registry Dashboard
The aim of this project was to pull data from a registry service using its API capabilities and present it in a user-friendly dashboard. I wanted to make sure the entire process was cheap, secure, and easy to upkeep, qualities that can be tricky to balance all at once.
I split the project up into 2 phases. Phase 1 covered transferring the data from the registry to a PowerBI dashboard, which was a bit of trail and error, but was successful. Phase 2 covered adding specific filtered to the dashboard depending on the user, and these filters would be added autonomously, without requiring users to manually log in every time. Phase 2 was a lot trickier, and s still incomplete.
Methodology
Phase 1
This really tested, and expanded upon, my technical skills. Through my astrophysics degree, I do a lot of data analysis and presentation through Python. However, the data in a university setting is reliable, easy to obtain, and consistent, this isn’t the case with this project! It was really interesting working with data that has real-world implications and it changed the way I think about my data analysis. I used Python code to make my API calls—the thing that gives me the data from the registry—which confused me at first, but everyone on my team was happy to answer all my questions. I was able to pull the data from the registry and produce a PowerBI dashboard that presents all this data simply.
Phase 2This really broadened my experience with different types of data, especially sensitive data and the security that must come with it. Phase 2 results are still inconclusive, but good progress has been made.
![]()
Applying the filters to the dashboard is relatively straightforward. Phase 2’s main difficulty is accessing employees’ names and departments, data which is quite sensitive and requires high admin permissions to access. Naturally, any workflows would have to ensure employee data is handled securely. In order to produce a successful dashboard, the current web registry data would need to be completely reorganised. To create a robust dashboard, the data—including employee data, stored separately—would also need to be accurate.
What I learned
I’m still a long way from understanding the ins-and-outs of accessibility testing, but this project certainly built up my confidence in the subject. It encouraged me to think about the logic of these guidelines in creative ways, to make it better digestible for AI. After all, how would I train an AI to test a guideline if I myself didn’t understand it? While the project didn’t produce earth-shattering findings, the findings are still inconclusive. We should continue to explore tools to make websites more accessible, especially as AI continues to evolve.
The dashboard helped my technical skills grow, and taught me to come at an issue from many different angles as certain avenues were rejected. The dashboard project taught me that there sometimes isn’t a “right” way to do things and that sometimes you have to juggle conflicting considerations in a project.
Overall, I’m really grateful I got to evolve in this way and I’m excited to see what future projects can accomplish!
-
Webdesigner Depot
- Meta Just Launched an AI That Uses Websites for You. That Could Be a Big Deal for Web Designers
Meta Just Launched an AI That Uses Websites for You. That Could Be a Big Deal for Web Designers
6 Best WordPress Plugins for Improving Website Accessibility in 2026
Accessibility should be a top priority when building a website. However, things can degrade over time. Clients adding content could forget basics such as ALT attributes and logical heading order. Best practices often fall through the cracks as a site ages. Thus, every website requires vigilance.
Part of the challenge is that it’s not always easy to identify accessibility issues. It often requires digging deeper to find and fix them. This is where the right WordPress plugin can be useful.
Some plugins allow users to adjust visual elements like font size and color contrast. Even better, some scan your content and alert you to problems. You might be surprised to find out how many issues can pop up in your theme and other installed plugins. The results may lead you to consider different options.
With that in mind, let’s look at some of the best WordPress accessibility plugins on the market. They won’t fix every issue, but they can help you learn and improve your site.
Accessibility Checker
Accessibility Checker isn’t a band-aid for your site’s shortcomings. However, it will add missing skip links, focus outlines, and form labels upon request. It also scans your site’s content and creates a laundry list of potential issues. It catches common problems, such as ambiguous link text and missing ALT attributes.
Like all automated tools, you may find some false-positive results. As such, a manual inspection is required to verify them. But the plugin offers tips for fixing any issues it finds. The free version scans your site’s pages and posts, while the pro version includes custom post types and other handy features.
![]()
WP Accessibility
Use WP Accessibility to fix common issues, such as missing language/text direction attributes, missing ARIA labels for navigation, and viewports that don’t scale. It will also enforce ALT attributes in the editor and identify media with missing descriptive text.
These are optional and can be activated as needed. The other big feature here is a front-end toolbar that controls page zooming and color contrast. This gives users more control over how they view your site.
![]()
Alt Text AI
We’re starting to see AI used for a variety of purposes, including accessibility improvements. Alt Text AI automatically analyzes uploaded images and generates an ALT description.
The feature can save you a lot of time and effort – just be sure to double-check to ensure the description is accurate. Note that the plugin requires purchasing AI “credits” to work. There’s a free trial for trying the plugin before you buy.
![]()
AccessiYes Accessibility Widget
Are you looking to provide visitors with accessibility options? This plugin adds a widget with a variety of optional feature modules. Users can change the font size and contrast. But there are also tools for switching to a dyslexia-friendly font, highlighting titles, and pausing animations.
You’ll also find a feature that helps you create an accessibility statement. Experiment to see which features will benefit your visitors.
![]()
SimpleTOC
Accessibility is about more than fixing issues – it’s also about adding accessible features. SimpleTOC creates a WCAG 2.2-conforming table of contents for your content. It’s a great way to help users navigate longer pages and blog posts. By default, the plugin adds zero CSS or JavaScript to your site.
Instead, it relies on HTML details and summary tags, which work natively in your browser. When it comes to accessibility, simple is always better.
![]()
Able Player
Media embeds, particularly from third-party services, can be difficult to use. Some are bloated with JavaScript and other code that inhibit accessibility. Able Player offers an accessibility-first solution and implements an HTML5 media player via a configurable shortcode.
It works with locally uploaded files and videos from YouTube and Vimeo. The shortcode offers several options impacting the style and functionality of the player.
Leave No User Behind
Accessibility is not a “nice-to-have” feature – it’s an obligation. It’s also an ongoing process that requires your attention. Thankfully, there are tools to help you find potential issues and fix the most common ones. The WordPress plugins above will help you in your quest. Bonus: Some will add accessible elements that benefit everyone.
No singular plugin can make your site fully accessible. But they can make your job easier. We hope you find a solution to do just that.
Website Accessibility Plugins at a Glance
| Plugin | Description | Primary Use |
|---|---|---|
| Accessibility Checker | Scans content for accessibility issues and can add missing skip links, focus outlines, and form labels, with guidance for fixing problems. | Accessibility auditing |
| WP Accessibility | Fixes common accessibility issues and adds front-end controls for page zooming and color contrast. | Accessibility improvements |
| Alt Text AI | Automatically analyzes uploaded images and generates ALT descriptions, with the option to review the generated text for accuracy. | Image ALT text |
| AccessiYes Accessibility Widget | Adds visitor controls for font size, contrast, dyslexia-friendly fonts, highlighted titles, paused animations, and other accessibility options. | Visitor accessibility controls |
| SimpleTOC | Creates a WCAG 2.2-conforming table of contents using native HTML without adding CSS or JavaScript by default. | Accessible content navigation |
| Able Player | Adds an accessibility-focused HTML5 media player for local files, YouTube, and Vimeo using a configurable shortcode. | Accessible media playback |
More Essential Free WordPress Plugins
The post 6 Best WordPress Plugins for Improving Website Accessibility in 2026 appeared first on Speckyboy Design Magazine.
-
Webdesigner Depot
- Figma is the New Dreamweaver: How Modern Prototyping Tools are Trapping Us in 2018
Figma is the New Dreamweaver: How Modern Prototyping Tools are Trapping Us in 2018
-
Website and Communications Blog
- Can AI do a content audit of my website? A review of different ELM models and AI products
Can AI do a content audit of my website? A review of different ELM models and AI products
Content audits are a long-time staple of the user-centred website toolkit, but they take time and effort to complete, which many website owners struggle to find. In my ongoing AI experimentation, I tried using AI tools to help me with auditing web content.
Every day brings a raft of new AI developments. When choosing how to use AI, I’m less sold on getting it to do creative tasks for me because I like doing those myself. Instead, in pursuit of freeing up my time, I prefer to use AI to help me with the tedious tasks I never get around to, the ones I know will take me longer than I think, the ones I put off again and again. Here’s looking at you, content auditing.
Websites are easy to grow but difficult to keep in check
When people come to the UX Service for help with their websites, they tend to use several phrases to describe their site. These have included: ‘It’s a mess!’ ‘It’s a bit out of control’. ‘It’s grown arms and legs’. None of this is unusual when you consider the lifecycle of websites. Over time, websites change hands. Pages once carefully crafted are easily forgotten as new editors take over. New content is created without knowing what’s already there. Very often, content needs to be published to a deadline and it’s quicker to publish a new page than seek out and amend an existing one. Seldomly do publishers want to get rid content that’s taken time and effort to produce.
Read some thoughts on content housekeeping by UX Service team members (current and past):
Digital housekeeping – applying content management practices to improve digital sustainability by me
Be a gardener by Ari Cass-Maran
Content Audit Findings and the 100k Challenge by Milo McLaughlin
How to get a grip of your website (and then keep hold) by Neil Allison
A content audit is the best place to start improving a website (not the homepage)
When people seek to bring order to disarray on a website it’s difficult know where to start, so typically, they start on the homepage with ideas to change images or add new content. While this gives sites a superficial makeover, it doesn’t really help site audiences in search of content. Fewer and fewer website audiences are starting out on homepages, instead they’re parachuting directly into site content from Google search and increasingly, from AI summaries. What does this mean? It’s more important than ever to make sure your web content is up-to-date, accurate, useful and relevant for your website users. Here’s looking at you, content auditing.
Read more about getting your content ready for AI from a recent Content Improvement Club session:
Auditing a website needs a methodical approach (which is where AI can help)
If audits are so important, why are they so easy to put off? Short answer, they can take prolonged amounts of time and concentrated effort. The larger and more complex your site is, it’s likely that there will be more content to review, and the more difficult it may be to maintain a consistent auditing approach. Going through multiple, long pages of web content, it can be easy to run out of the time you’ve allocated for your audit. Breaking the audit into chunks may lead to different results from different sessions as biases creep in. Bringing colleagues in to help can share the load, but can also introduce new perspectives and contradictory auditing decisions. There’s a need to maintain ruthless objectivity, to counter human subjectivity and avoid errors infiltrating. Here’s looking at you, AI.
If you can plan and describe a website content audit, you can ask AI to help you do it
Website content audits can be done for many purposes, but commonly, doing a content audit involves making decisions about what content to keep, what needs to go and what needs to be changed – all in pursuit of reaching a future state of your website. A good way to decide what content to keep is to consider who it’s for and the purposes it serves. If a piece of content doesn’t meet audience needs and doesn’t align with the site purpose, then it’s probably a candidate for deletion. A good content audit of a website therefore typically requires several things:
- An inventory of every piece of content in the site. Typically arranged in a spreadsheet, with one row per webpage. Can be organised into sections or content types, or grouped by root URL
- A note of the site audiences, ideally in order of priority (answering the question ‘Who is this site primarily for?)
- A list of the main reasons those audiences visit the site (answering the question ‘What tasks do people complete on this site?’) together with a list of the main goals of your site (answering the question ‘What do we want people to do on this site?’)
Considering each of these things as different pieces of data, where item 1 is data to be audited, items 2 and 3 are factors or auditing criteria used to decide what happens to those data (typically one of three outcomes: ‘Keep’, ‘Delete’ or ‘Modify’), I reasoned that I could give AI these data, tell it what a content audit was and and ask it to complete this process for a given website.
I experimented with ELM to help me do a content audit of a website
The University’s AI platform, ELM was the natural place to start experimenting with applying AI to aid content auditing. The ELM interface allows you to input a prompt, as well as add additional files and data sources. It also allows you to select different models to handle queries. I was curious to see the differences between the different models – both non-reasoning ones and reasoning ones so I needed to design a prompt that would work for both.
Read more about ELM and its models
ELM new model guides (University log in required)
Being mindful of the environmental cost, I wanted to start with a small AI model (Llama 3.3)
AI comes with a significant environmental cost, which is highly dependent on the LLMs you use. Powerful models with more reasoning power are especially resource-intensive to run, so to avoid unnecessary wastage of tokens and other resources I’ve found it’s sometimes best to start with a smaller model and size up accordingly, as the need arises. The trade-off is that smaller models have limited reasoning power, however, so the responses they provide and the tasks they are able to complete can be limited.
Based on my previous experience of using AI and thinking about its potential application to a typical content auditing process, I had a hunch that providing a small model with something like a site inventory (such as a XML sitemap) and detailed data about website audiences and purposes could overload its context window and produce inferior results.
I therefore decided to begin with a lightweight prompt ‘Can you help me do a content audit of this website? (with a link to the website)’ to give a small model something manageable and learn how it approached handling the query. I chose a website that the UX team had recently worked on, so I was familiar with its content, and I entered the prompt, starting with the Llama 3.3 model – an open weights model (costed on computing power rather than per-token usage) which is hosted in University data centres (instead of being cloud-based). I toggled on the option to include web search so ELM was able to access the website.
The same prompt to different ELM models produced varied results
Having starting with Llama 3.3, I moved on to other models: Open AI’s GPT 5 and then Anthropic’s Sonnet 4.6. To assess and critique responses from each, I adopted the mindset of a person reluctant to begin a content audit and looking for AI help to kick-start action on this, and used this as a roleplay to review and compare the responses.
The response from Llama 3.3. was too generic to convince me to start auditing
Despite a glitch in formatting the response, Llama 3.3. provided some general information about content auditing. Its response included an initial assessment of the site, which made objective judgements of the homepage (assessing it as ‘well-structured, with a clear introduction’), the navigation menu (labelling it ‘easy to use with links to key sections’), content quality (noting it as ‘high-quality, informative and engaging’) and accessibility (pulling out that the site had an accessibility statement).
The response then acknowledged that in order to do a thorough content audit on the site in question there was a need to provide guidance on the aspects to focus on, and rounding off, the response noted some of the aspects a typical content audit would examine: content quantity, content quality, accessibility and consistency across different parts of a site.
Reviewing this response, I felt that if I was a site owner looking to improve my site, this response could very easily persuade me that I didn’t need to bother auditing it at all – and I wasn’t left any wiser about how to meaningfully provide guidance on the aspects to focus on if I did decide to proceed with an audit.
Likelihood to convince me to audit: 3/10
Open AI’s GPT 5’s response was detailed and thorough but a bit overwhelming
As would be expected from a reasoning model, the response when I used GPT 5 was more detailed than Llama 3.3’s. Arranged in two sections, the first part included preliminary observations using the site URL provided – which were split into the following categories:
- Information architecture and navigation – commending the site’s positioning on user intents, yet suggesting improvements with more explicit audience pathways and call-to-action signposting
- Content coverage and freshness – using the site’s range of content types to assess content structure and assessing freshness based on recency of news items
- Call to actions – acknowledging that the site had were multiple calls-to-action which could be combined into primary CTAs for each audience
- Accessibility and usability – calling out the need for more meaningful and less duplicated alt text on the site images
- Trust and governance signals – recognising the role of the site’s strong branding to demonstrate authenticity
- SEO – suggesting the site’s page titles and meta descriptions were reviewed for relevance
The second part of the response outlined a plan for a full audit. The plan began by posing three questions to be answered:
- What are the primary goals? e.g. increase visitors, boost traffic, showcase outputs
- Who are the priority audiences? (with suggestions of the different groups)
- What’s in scope? (suggesting either the entire site or specific sections)
The response then provided a suggested series of 7 steps to follow to complete the audit:
- Inventory and crawl (with detail of the inventory to start with and the tools to complete the crawl)
- Editorial quality review (with detail of criteria to score each page – such as inclusivity, accuracy, audience-fit etc)
- UX and IA review (with suggestions to evaluate navigation labels and connections between content and pathways to achieve top tasks)
- Accessibility (with suggestions of accessibility checking tools to use as well as manual checks to complete)
- SEO and technical (with suggestions to check data points like metatags, internal links, robots files and performance)
- Analytics (with suggestions to use analytic data such as bounce rates, page views, site searches etc)
- Recommendations and roadmap (detailing prioritisation measures to make the identified site changes)
It rounded off suggesting a template structure for the content inventory (and offering to create this template as a Google Sheet), an idea for a scoring rubric, and reiterating different tools to use (naming products like Screaming Frog, Google Analytics and SEMrush). To conclude, it offered to do the audit, requesting answers to the three initial questions and asking for access to a sitemap, external tools and governance documents (such as style guide and brand voice guidelines).
Reviewing the response, which was presented as text content, I found it a bit too much to scan and digest, and putting myself in the place of someone facing content auditing with some reluctance, it felt that this large amount of detail could be off-putting to even start the process. I could appreciate the relevance of suggesting of external tools, but knowing that each of those would require setting up accounts and logins, as well as going through a process to integrate with Open AI, it had the effect of making me mentally push content auditing to the bottom of a to-do list.
Likelihood to convince me to audit: 6/10
Anthropic’s Sonnet 4.6’s response gave structured guidance which was easier to follow
The output from the Anthropic model stood out compared to the others from ELM since it was not just plain text, instead, it had been structured with headings, tables and icons. This made scanning and digesting this response much easier than the others.
The response was structured into 10 sections, as follows:
- Site overview – table summarising the site name, owner, primary purposes and date of confirmed content
- Information architecture – list of the top-level navigation elements with an assessment of what worked well and issues identified in a bulleted list
- Content inventory – table of pages, with noted audiences, details of last update (if known) and inferred status (on a red, green and amber scale)
- Calls to action – list of CTAs on the homepage, with assessments and recommendations
- Content freshness – table containing list of most recent items in each section and related assessment
- Accessibility – list of accessible features that were present, table of items that needed checking and recommended accessibility tools to make the assessment
- SEO and technical – table containing an SEO assessment, considering elements like meta descriptions, structured data, mobile responsiveness – each with an allocated status, associated notes and combined recommendations
- Content quality and tone – list of observations and recommendations
- Priority recommendations summary – table of priority actions with an effort/impact score
- To complete the full audit I need – list of requirements to complete the full audit (including sitemap, CMS page list, Google Analytics data, etc.)
Content within each of these sections was comparable to that included in the GPT 5 response, but in the Sonnet 4.6 response, these sections referred directly to information from the site in question – for example, instead of making general assessments of site aspects like navigation and content coverage, it contained direct detail about the site itself with mention of specific pieces of content, noting what was already known (for example, referring to issues noted in the accessibility statement). Arranging this in tables with use of icons and red, green and amber priority indicators made it easy for me to pinpoint what to address and with what urgency, and having this consolidated in the final table was easier to parse than reading it in text format (as in the GPT 5’s response).
Reviewing this response from Sonnet 4.6, it was the best of the bunch from ELM, it contained enough detail to help me get started but not so much that it was overwhelming. Putting myself in the position of a time-poor site owner unsure where to start, I had clear pointers of the priority areas and a mix of quick wins and bigger tasks to choose from.
Likelihood to convince me to audit: 7/10
Three sets of two side-by-side screenshots, showing the output from Open AI GPT 5.5 (on the left) compared to the output from Anthropic’s Sonnet 4.6 (on the right) showing Anthropic’s more structured and visually appealing approach to presenting the responses
As well as ELM, I experimented with Chat GPT and Claude to provide content audit help
Models within ELM can also be accessed through interfaces provided by AI products. Two of the best-known AI products are Chat GPT (by Open AI) and Claude (by Anthropic). I was curious to see the responses each of these products would provide in response to my query asking for content auditing help so I prompted each of them in the same way. In both cases I used the free versions.
Chat GPT gave a suggested approach and produced initial findings
The response from Chat GPT was comparable to the output from ELM choosing an Open AI model, but the response was structured and annotated with tables and icons, in a style similar to the Anthropic response. It began with a suggested audit approach which set out different areas to consider and related questions. In the next section (headed ‘Initial observations’) it contained an analysis of the site itself, which included site strengths and highlighted the following six areas for improvement on the site in question:
- Homepage is quite academic – pulling out some audience questions that would be relevant to be answered on the homepage instead of the content that was there
- Navigation could be more task-focused – noting that the current navigation was driven by organisational structure rather than tasks users would want to complete
- News archive – picking out the need for recent articles
- Calls to action – acknowledging that many of these are worded to provide information not prompt an active response
- Content consistency – advising a uniform page structure for easier reading
- Audience segmentation – recommending clearer delineation between groups of site users
The response concluded with an example audit table and some content recommendations, organised under ‘Keep’, ‘Improve’ and ‘Review’.
Reviewing this response as a whole, I liked the up-front suggestion of an auditing approach and the example audit table which was then supplemented with detail about the site itself and recommendations relevant to different aspects of the site in question. This helped me visualise what the audit outputs could look like, and I could see ways to get there.
Likelihood to convince me to audit: 7/10
A screen showing the output from Open AI after being prompted for help content auditing. The suggested audit approach laid out in a table with columns for the different areas of auditing and associated questions to ask in the right-hand column
Another screen showing the output from Open AI after being prompted for help content auditing. An example audit table is laid out with rows for each URL, and columns containing associated purpose, audience, quality and recommendations.
Another screen showing the output from Open AI after being prompted for help content auditing. Content recommendations are laid out with colour coding for ‘Keep’, ‘Improve’ and ‘Review’.
Claude presented interactives to actively take me through an audit process
Anthropic’s Claude interface took a different approach to the other AI products, immediately asking about the main goal of the audit with options to pick. I picked ‘full inventory’. It then asked the desired breadth of the audit with another set of options, from which I picked ‘full site crawl’. The next screen asked me about the output format, and I picked ‘spreadsheet’.
From top to bottom, the interactive screens produced by Claude asking about the main goal of the audit, the breadth of the audit and the format for the audit output. Each has multiple choice answers to select
After approximately 2-3 minutes, with a running commentary of what was being done, Claude presented a list of ‘headline findings’ of bugs, orphaned content, out-of-date content and broken content (dead links, incomplete calls-to-actions etc). It also produced a downloadable Google Sheet with two tabs – the first containing a summary of the issues to be fixed, their locations and a reason why they needed to be fixed, the second with a full inventory, with one row for every URL in the site and columns logging the page title, content type, date, status (with colour-coded options: ‘Keep’ (green), ‘Update’ (amber), ‘Rewrite’ (dark amber), ‘Review’ (blue) and ‘Critical’ (red)) and recommended actions for each page.
Screenshot of the audit output spreadsheet produced by Claude, showing one row per page URL and different columns logging content types, date, status and recommended actions.
Reviewing this response, it was by far the most effective at making me feel I was starting the content auditing process and supporting me through it. Being presented with the opportunity to answer questions upfront meant I could control how the audit went, and having a spreadsheet created for me to review saved a lot of effort making this from scratch by scraping the site for a sitemap and page metadata.
Likelihood to convince me to audit: 9/10
Conclusion: If you’re putting off auditing your website, try getting AI to help
If you’re looking to improve your website, doing a content audit is one of the best steps you can take – working out what you have, what’s working and what’s not will put you in a strong place to move forward and make positive changes. Depending on how well you know your site, and how much time and resource you have to spend on it, you may appreciate some help to get started auditing its content.
From my quick experimentation with the different AI tools available I learned that, with the exception of the small non-reasoning model, each AI product offered something to help initiate the content auditing process of a website. At a basic level, asking AI to look at your website will pull out something you may not find yourself such as an out-of-date page, an irrelevant CTA or an accessibility glitch. AI can also take a zoomed-out look at your site that you may be too close to adopt yourself – such as reviewing your navigation pathways, appraising your audience segmentation or analysing the consistency of your content voice and tone.
If you’ve never audited a website before, AI can offer a lot of guidance to get you started, and whether you choose to do it yourself taking recommendations from the AI on tools and/or processes or whether you prefer to hand the heavy-lifting to AI to get your audit spreadsheet started – leaving you to deal with the more nuanced decisions that require specialist knowledge and experience, these tools can save you time and effort and may just be the nudge you need to do this all-important website maintenance task.
-
Website and Communications Blog
- Curiouser and curiouser. A year’s update on the Curious Edinburgh project
Curiouser and curiouser. A year’s update on the Curious Edinburgh project
It’s been a year (and two months) since I started to migrate Curious Edinburgh, and the newborn website is live!
To re-introduce, Curious Edinburgh is an open access platform which houses digital tours of Edinburgh and the Lothians. The tours are broken down into Community, Coastal and tours on the History of Science, Technology and Medicine. All 26 of them, long and short, highlight a particular dimension of Edinburgh’s cultural and scientific heritage. Users can walk the tours physically, using Curious Edinburgh as their guide, or virtually.
Here’s an overview of how Curious Edinburgh migration progressed throughout this time and the discoveries I’ve made along the way.
What changed
My assignment was to migrate CE tours from WordPress to ArcGIS StoryMaps. As with any digital migration, I sought to improve content and functionality – not simply transfer them. I particularly focused on upgrading the project’s digital accessibility and user experience. On top of designing a new layout for the webpages, I incorporated interactive maps into each tour. They follow along with the text, situating the user geographically, and allow for easier navigation. All tour points are also assembled into interactive Maps of Contents at the head of each tour. Maps apart, I smoothed the creases and filled in the gaps: proofread every line, sourced new images, replaced or enhanced sources, created feedback sections, and wrote alt text to each image, video, map and embed. Besides accessibility, this has enhanced CE’s cohesiveness and visual appeal.
Excitingly, just as I was wrapping up migration in early June, Curious Edinburgh received a request from the Consulate General of the US in Edinburgh to host a new tour. The tour would celebrate the 250 years since the Declaration of Independence was signed and the United States founded in 1776.
This task marked a change of pace, giving me an opportunity to create a tour directly on StoryMaps. I was happy to be more actively involved with the content planning side of CE. In a back-and-forth with the Consulate, we’ve outlined the tour’s contents. The stop order in particular took careful arranging, since the trail spans the architectural heritage of Old Town, New Town and Leith. By 4 July 2026, we delivered a new publicly available tour, the USA 250 Anniversary Trail. It highlights the diplomatic, intellectual and labour connections between Edinburgh and the United States.
Rapid-fire stats
Tours on CE: 26
Tours migrated: 25
Tours created: 1
Best tour (highly subjective): Granton, all the Coastal tours, History of Public Health
Maps created: 422
ArcGIS products used: 4 (and more by the EDINA team, who created the landing website of the new platform).
Content highlights
Out of all trails, the tour around Granton was the largest and most daunting to migrate. Granton is one of Edinburgh’s northern waterfront districts – less visited than Leith, less gentrified than Newhaven. It has many new apartment buildings and a B&M home store. What could there be to see?
That’s what I thought, too.
Turns out, Granton is a remarkable hub of Scottish industrial heritage. From quarries to street art, this tour takes the reader through centuries of history and modern-day change. Besides, the tour is assembled by Grantonians themselves, narrated with warmth and illustrated by archival images and local artwork. I migrated it with great pleasure, if gritting my teeth at 100-something images that needed fresh alt text.
History evidently doesn’t discriminate – it happens everywhere. Yet, if you ask an Edinburgh resident ‘Have you ever been to Granton?’ chances are they will say no and maybe follow up with ‘Is that in Fife?’
Maybe the Granton tour will make amends.
Gasworks by Harry Mafuji depict the Granton Gas Holder
People highlights
Luckily I have crossed paths with many new people during my internship. I would like to highlight two things.
The first one happened when I reached out to an independent Edinburgh tour guide, asking to reuse his photo for the History of Public Health tour. I expected a ‘no’ or a ‘sure’. What I didn’t expect was an enthusiastic response which acknowledged the significance of CE for Edinburgh’s heritage and tourism experts. I got my copyright permission and positive feedback to boot. It’s nice to be working on something people actually use.
My second highlight is last summer’s cohort of interns, many of whom returned to LTW this summer. Apart from being great company, they were also the first test subjects for my working webpage designs. Throughout last summer, upon my request, they submitted ingenious test comments for the tours (through Survey123), so that I could create initial data sets for setting up feedback moderation (in Experience Builder). In fact, these test comments were so creative that one of the CE team members asked me, very apprehensively, if we had accidentally catapulted the webpages into public access.
Data table chaos on a feature layer of the History of Witchcraft comment section
What’s next for Curious Edinburgh?
As the migration breathes new life into the project, Curious Edinburgh remains a living database for the Scottish capital’s past and present. A tour on the history of AI, currently in the works, should make a good addition to its history of technology section. I am also hopeful that soon CE users will be able to explore Edinburgh’s volcano more closely as a tour on Arthur’s Seat geology is integrated into the project. Finally, as 2026 marks the 300th anniversary of the Edinburgh Medical School, CE stays an excellent place to explore the history of the city’s healthcare sector.
Parts of the migration process were out of my scope, but could be tackled in the future. Here is just a glimpse of them. Digital sustainability: compared to the WordPress version, many webpages have increased in weight (mainly from heavy scripts). Mobile-friendliness: CE has an app which was not migrated/renovated, which leaves the question of a truly mobile-adapted Curious Edinburgh in the air. And a user-friendly mobile version is quite important for a walking guide. Digital preservation: how should the WordPress version be managed and maintained?
Waving goodbye
With the handover documentation completed, editing access transferred, and the latest tour completed, it is time for me to wave goodbye to a year’s work and ISG, and move on with a new project. We’ll see what that’ll be. (Exciting.)
There is a lot of knowledge to be gained from Curious Edinburgh, and more still from its creators and contributors. I’m certainly grateful for the opportunity to find out.
You can pay Curious Edinburgh a visit here.
A test comment on the History of Geology tour
Curious links
Why Your Favorite Websites Look Like 2005 (And Why You Secretly Love It)
#226 – Jessica Lyschik on Why Accessibility in WordPress Themes Is Easier Than You Think
Transcript
[00:00:19] Nathan Wrigley: Welcome to the Jukebox Podcast from WP Tavern. My name is Nathan Wrigley.
Jukebox is a podcast which is dedicated to all things WordPress. The people, the events, the plugins, the blocks, the themes, and in this case, why accessibility in WordPress themes is easier than you think.
If you’d like to subscribe to the podcast, you can do that by searching for WP Tavern in your podcast player of choice, or by going to wptavern.com/feed/podcast, and you can copy that URL into most podcast players.
If you have a topic that you’d like us to feature on the podcast, I’m keen to hear from you and hopefully get you, or your idea, featured on the show. Head to wptavern.com/contact/jukebox and use the form there.
So on the podcast today we have Jessica Lyschik. Jessica is a longtime member of the WordPress community who’s been working in the ecosystem since 2015. She’s spent years learning and advocating for web accessibility, both as a developer and as an active community participant, joining agencies, working on theme reviews, and helping improve standards.
Many theme creators assume that making themes accessible is an intimidating task, but Jessica’s here to show you that achieving an accessibility ready WordPress theme is more straightforward than you might imagine.
Her WordCamp Europe 2026 presentation, accessibility in themes, easier than you think, aimed to demystify the requirements for accessible themes. Explaining what the WordPress guidelines mean in practise, where the low hanging fruit is, and how both block and classic themes can reach accessibility ready status with manageable efforts.
We talk about the personal and moral journey that brings developers to accessibility. The technical hurdles and documentation challenges, and the ways in which things like AI agents are putting accessibility in the spotlight for everyone.
Jessica talks about practical steps that quickly improve accessibility, like using correct HTML tags, adding alternative text to images, and configuring skip to content links, and shares why building accessibility in from the start saves time and effort down the road.
We also explore the differences, and possible advantages, of block themes when it comes to accessibility, and why theme guidelines work the way they do, and the importance of interdisciplinary awareness across SEO, design, and content teams.
Jessica mentions helpful resources, influential leaders in accessibility, and the ongoing need for documentation improvements to help everyone level up.
If you’ve ever felt overwhelmed by accessibility requirements, or wonder why they matter, and how you can build better WordPress sites that work for everyone, this episode is for you.
If you’re interested in finding out more, you can find all of the links in the show notes by heading to wptavern.com/podcast, where you’ll find all the other episodes as well.
And so without further delay, I bring you Jessica Lyschik.
I am joined on the podcast by Jessica Lyschik. Hello, Jessica.
[00:03:39] Jessica Lyschik: Hi Nathan.
[00:03:41] Nathan Wrigley: Nice to have you with us. This is my second interview at WordCamp Europe 2026. We’re in a beautiful, big media room. I’ve got to say, this is one of the nicest spaces I’ve ever had for these kind of interviews, so that’s really nice.
Jessica has already done, I want to say presentation but maybe it was a workshop. I’m not sure.
[00:03:57] Jessica Lyschik: No, it was a regular talk actually, yeah.
[00:03:59] Nathan Wrigley: Okay. And how did it go?
[00:04:00] Jessica Lyschik: It went super well, except for my slides went missing in between. That wasn’t so great. But the audience was very respectful of that, and I made a bit fun of it, so they laughed for a second and I tried, the media guys tried to fix that. We got it fixed in the end. I would’ve winged it anyway because I, like I knew what was coming up. But it’s always good to have your slides. It’s like seeing them, because for me it’s also visual reminder. It’s like, I need to see what I’m talking about, so I’m not losing track of it. But yeah, this was just a little technical hiccup. But overall I got very great feedback so far on my talk, and I’m very glad.
There were also quite a lot of people. I did not expect this many. And that makes me just super happy that people are actually interested in this topic, although it is sort of scary for some of them if they even like try to touch this topic. We can probably get into the details later. Yeah, just overall like, what does it do? Why do I need that? These unanswered questions that they have that they were like, ah, no, I’m not really interested into that.
[00:05:01] Nathan Wrigley: Oh, that’s nice a big reception.
[00:05:03] Jessica Lyschik: Yeah. And that’s just great to see because I think just as we all grow older, and I even noticed that, and I’ve said that in my talk, like I kind of get to appreciate when a website is accessible. I mean I’m still have a long time to go, hopefully in my life, but I start to appreciate the small things that make just browsing websites easier, to be honest.
[00:05:23] Nathan Wrigley: So I guess we should introduce the subject and then give you a chance to introduce yourself because it feels like in this context, the subject at hand, it’s important to know that you know what you are doing. It’s not, well, I suppose it’s a general skill in that it should be something most people know an awful lot about. But I fear that that’s not the case.
So the presentation that you’ve just given was called accessibility in themes, easier than you think. That’s nicely phrased. Let’s get them through the door.
And then the blurb that went with that, I’ll just read that into the record then everybody knows what we’re talking about. So it says, many theme developers assume accessibility ready requirements are hard to meet, but that’s rarely true. This session shares practical insights for real theme reviews, and shows how both block and classic themes can reach accessibility ready status with manageable effort.
So that’s the context of what we’re going to talk about today. However, as I just alluded to, could you just tell us a bit about you, how long you’ve been using WordPress, and then I guess if you want to focus a bit on your accessibility credentials and what you’ve been doing in that space.
[00:06:23] Jessica Lyschik: Yeah, of course. So yeah, I’ve been using WordPress, I think I started around 2005 or 6 already. So like dipped my toes into it, played with it around, just got a feel for it. But actually professionally, I started out in 2015 in the WordPress ecosystem.
Before that, I already joined the community. So I was working at another place that did not use WordPress before. And then in 2015 I joined a WordPress agency. Today they’re called Syde, for anyone who’s wondering. And ever since I’ve been into WordPress that long.
And accessibility in that case I have, I think it was a gradual process more of. It was not just like, I’m now doing accessibility. That just didn’t happen. It was, I learned it over time. And when I started learning about how to create a website accessibility was absolutely not a thing. No one cared about it. And it just became more and more aware for people, for developers, especially in the past couple years. I think we still have some way to go but like, as I said earlier, there were so many people interested in my talk. So I think we’re now at a pace where things get really interesting for many more people.
And yeah, I learned a lot along the way. Made a lot of mistakes along the way. But I’m glad I’m learning this. I’m still learning. So it’s always something that you continuously learn, because I think the hardest part to grasp for people is that, if you are abled, it’s like you can see, you can hear, you can navigate a device with your own hands, all stuff like that, you take it for granted.
And if you suddenly see or people tell you the perspective of like a blind person, a person who’s deaf, a person who may not be able to use a device like you do, maybe have a hand injury, or no hands anymore, that’s also happening. Then you start to wonder, okay, how do these people actually like use websites or use their phones or computers? And there are many different ways to do that. And I think if you have the chance to learn about this, it is absolutely eye-opening.
You can also then, there was a talk at WordCamp Leipzig this year, but also last year, I attended last year, by a blind person. And her brother was also blind. He was a developer. And they shared like how bad some websites are, and how they struggle to like get the information out of the website, and what crazy, crazy stuff people are doing to their websites that do not make it accessible for these people.
And then you are sitting there and wondering, oh my God. And sometimes I have to say, I even did this in the past and I didn’t know, but I’m glad today that I learned about this and make a better web essentially. Yeah, that’s why I’m here sharing my knowledge.
[00:09:11] Nathan Wrigley: It kind of sounds for me, so when I talk about accessibility, there’s always two strands to it. There’s like this legal bit where the governments are increasingly talking about things that will happen to you as a company that builds websites if you don’t follow guidelines. So that’s one side.
But there’s also this moral side. There’s the side of, we ought to do this despite what the law says. You know, it’s just a necessary thing. And it feels to me as if your journey in this was a moral one.
[00:09:38] Jessica Lyschik: More of, yes.
[00:09:39] Nathan Wrigley: Yeah, there was a definite need here. You know, in the real world when you see somebody, let’s say somebody who’s sitting in a wheelchair and they’re trying to get into a post office and there’s a step that they can’t get over, there’s no bit of you which doesn’t see that as unjust. Every bit of you says that character can’t get over that step. That’s wrong.
And yet, the bit of the world which is becoming increasingly the way that we interact, you know, we book flights, we file our taxes, we do our banking, we, all of these things, they’re completely invisible.
Most of the time we’re doing the internet by ourselves. You know, we might be sitting on a train, but nevertheless it’s a solitary activity, or we’re in our own home or whatever. And these pitfalls, the equivalent of the step in front of the post office is totally invisible.
And it also seems that the voice of the people whose lives are made more difficult is just drowned out. Somehow that anger that they must feel never seems to rise to the top quite enough that we all take the necessary steps.
I don’t know if any of that landed, and there was definitely no question there, but I’ll hand it back to you if any of that resonates.
[00:10:49] Jessica Lyschik: No, I think you, you’ve put it absolutely right. And the invisibility is the thing, because a step for us is visually, like we see it I mean. If you’re blind, you’re not seeing it. But let’s put it away for a second. But in the web, the invisibility is like the key thing. And I just talked to Anne-Mieke Bovelett about, who’s doing another accessibility talk this afternoon. She told me about like a company where they put effort into their website, making it more accessible. And their sales actually increased. So it can definitely help. This is just one example.
But there’s also a new player in the field that will probably even increase the interest in accessibility, and that is AI agents. Because AI agents, they do not see a website as we do visually. They rely on that the website is technically built correctly. Google actually just last month announced that they will focus on this. They will focus on the accessibility for the AI agent. I have put a link in my slides to that document. This is basically, I think something that will be easier to grasp for people for some weird reason. But it’s made more visible to them because if an AI agent cannot read your website, and I know we are probably still at the very beginning of this AI agent stuff, but I think this will increase over the next couple months or even years.
[00:12:14] Nathan Wrigley: That’s really interesting because when an individual, let’s go back 10 years, when an individual is creating a website, every single bit that you have to achieve is a minute of work or another minute or 20 minutes or an hour or what have you. And so there was this whole thing of just building the website, especially when page builders and things like that came along, just building the website to see what it looks like. And that whole accessibility layer just basically gets ignored.
However, that’s what you’ve just said is curious because the AI agent building the website, to the AI agent, that’s kind of no extra work to get it right, if you know what I mean? If it’s configured to do all of the bits correctly, I’m using air quotes around the word correctly, then in theory it should be quite a good custodian of accessibility when it’s building things. I guess only time will tell whether that actually happens.
[00:13:08] Jessica Lyschik: Yeah, but it’s also for like, not the agents itself building, but also the agents visiting your website. Especially if you do like, I think shopping will be the one thing that if you say, hey, I don’t know what the best coffee or what, this is like a good topic. Yeah, okay, here are three options. And then, okay, buy me option one, a kilo of these beans or whatever. The AI agent, if the shop is accessible, the AI agent could do the shopping for you. This is where things are going and progressing towards, that you are not actively anymore the person who actually goes to the online shop, puts it in the cart, goes to the checkout and does all that stuff for you. But if the agent knows all that, it can do it for you.
[00:13:50] Nathan Wrigley: Can I ask a question then? Because I may have, I think I’ve understood what you were just saying and curiously, I’ve never had that thought, the one that you’ve just expressed. I want to know if I’ve got it right. Are you saying that in a world in which we increasingly ask AI to achieve things on the web for us, if it’s built with accessibility in mind, it’s more likely to be able to achieve the result of, let’s say, buy me a kilo of coffee.
[00:14:14] Jessica Lyschik: Yep.
[00:14:15] Nathan Wrigley: That’s so interesting.
[00:14:16] Jessica Lyschik: Yeah because like, Anne-Mieke, whom I just talked about, shared a long document with me recently and I was just reading through it and was like, yeah, of course. Of course, if we technically do things right, we use the right elements, we do the right descriptions for everything that a computer, because AI agent is just a computer. Like assistive technology, like a screen reader who needs to read the right structure out of it and to fit the right content. But also is able to interact with stuff, like click on that button, put that in the cart, go to the checkout and so on. It’s basically the same. An AI agent is a screen reader.
[00:14:53] Nathan Wrigley: Yeah, that’s really interesting. I’m thinking of a map where I’m trying to get to a destination, but the map has no directions. Imagine a scenario where we set off from one place and our destination is here. What you are saying is all the instructions in between to get from the start to the end can be read if the HTML and all of the bits and pieces wrapped up in that are correct. I had never had that thought before. That’s so interesting.
[00:15:17] Jessica Lyschik: Yeah, that’s very interesting. And I did not focus too much on this topic in my talk, but I wanted to put it in there at least in one slide to give like the food for thought that people can actually think about it because this is like what’s hyped right now. I have not tried out this whole agent thing yet, but like from a developer perspective, I can totally see that this is something that will increasingly help AI agents to achieve stuff.
[00:15:41] Nathan Wrigley: Yeah. And presumably make it so that a whole tranche of people who struggle with the web as it is currently might be able to interact with their voice or whatever other technique they use. We’ve completely gone off the rails, but that was such an interesting aside, thank you.
[00:15:58] Jessica Lyschik: Yeah, I think this is something interesting to share. And as I said, I wanted to focus more on the technical details in my talk, so I left it kind of out. But I think it’s a great opportunity to share it here with you.
[00:16:08] Nathan Wrigley: Yeah. That was lovely. Thank you.
So let’s go back to the WordPress bits and pieces then, and I’ll just do the title again because hopefully that’ll refresh it in listeners’ minds. Accessibility in themes, easier than you think. Dear listener, if you’ve been using WordPress for any length of time, you’ll know that the themes still plays a giant part in the structure of your website and the way that people experience it.
So where are we at then in the year 2026? Does the theme still represent a huge part of accessibility? In your experience, is it easier than most people think to get an accessible website in the year 2026? We’ll get into block based themes and classic themes and all that in a minute. But essentially what I’m asking is, is it an easier thing to get right than most people imagine?
[00:16:51] Jessica Lyschik: Yes, because I think what scares people off from my own experience, there are requirements to get the accessibility ready tag in the wordpress.org theme repository. And these requirements, if you first read them, they’ll sound a bit cryptic and you do not really understand what they actually mean.
In my talk, I was trying to combine this, what the requirement says with what is actually meant by that. Because right now, and this is something I would like to improve for the future, I’ve already talked to people about this, and I will have another chat with Rian Rietveld about it later, or tomorrow. Let’s see when we can make that happen.
Because right now the requirements read like, okay, this must be achieved. This is what the website should do. Then there are some testing instructions, but you’re not told how to achieve it. What do you technically need to do in order to do that?
I noticed this while I was reworking. I found out about the requirements also just a month ago because the requirements got updated. I have a theme in the wordpress.org repository and I tried to apply these new rules and have another fresh look at it. I got the accessibility ready tag for this already when I first got the theme into the repository. But like it was a good refresher to like go over all the requirements because they have slightly changed a bit, they added new ones.
When I was there, I was like, okay, like I understand this now because I have learned about accessibility over the past couple years. For someone who is fresh to this topic and doesn’t know too much about it, it’s hard to understand. Because there are some descriptions of things like, basically what it means is that you need to use, for example, the right HTML tags, header, footer, the main tag. We have section and aside, which are available in HTML 5. But the requirements does not say this explicitly.
And I think this is where probably most people have gotten stuck in the past, because they did not understand like, what is actually required from me technically? Because the texts are not so much focused on that. And this is something I would like to contribute as well, to give back and to enhance. So it’s not there yet, but hopefully sooner than later we can add all this information so it gets even easier for people.
Because if you’ve done a website and you know about the HTML, you know about maybe a little bit of CSS, you know how to achieve this. You just need to connect the dots to what is relevant for accessibility and how do you do this in your HTML essentially.
[00:19:20] Nathan Wrigley: Yeah, I guess that’s a bit of a shame really, isn’t it? Is that the documentation is difficult to follow because I feel that accessibility is one of those things where if something is difficult it can get dropped basically.
[00:19:33] Jessica Lyschik: Yeah, people won’t do it.
[00:19:34] Nathan Wrigley: Yeah, because the majority of people browsing the internet can browse the internet despite your accessibility efforts, that will be the standard that they’re aiming for in most cases. So if it’s difficult to achieve these things and the documentation’s not really straightforward, every time somebody comes across a question and thinks, I don’t really know the answer to that, probably the quickest thing to do is just to, ah, push it to one side and not press through. But you obviously have and made it a bit of a goal.
So is there a particular accessibility requirement that developers in your estimation kind of overestimate the difficulty of? What I’m asking here really is about some low hanging fruit that you know about. In the scenario that we’ve just described where it’s easy to get put off and to sort of say to yourself, okay, I can’t do this. I’m wondering there are some sort of quick wins that you could describe that people could maybe achieve within the next half an hour, once they sat down at their machines?
[00:20:27] Jessica Lyschik: Yeah, I think there are definitely some. There is like underlining text in your main content, just underline the text. It’s one line of CSS, text declaration underline. For links, obviously, not for the entire text.
And there is like, as I said, the HTML tags. With block themes, it’s super easy. For example, you just need to configure that correctly in the editor, or use the correct template part and it’s basically done for you. Core does that. This is one advantage of block themes, but we can dive into this deeper later. Or the skip to content links also in block themes.
As an example, in block themes it is just like putting the content block in a group and assigning the main HTML tag to that group. And WordPress does the rest for you. It’s just like assigning this one little setting correctly and then you get automatically a skip a content link for block themes.
[00:21:18] Nathan Wrigley: Yeah, but curiously, if you didn’t know that small fact, that WordPress would handle that for you, if you don’t know, you don’t know. And you’d presumably go around the houses trying to figure that out for yourself and implement some custom version of that thing. Whereas in fact, what, three clicks, four seconds and you’re done.
[00:21:33] Jessica Lyschik: It’s super easy, yep.
[00:21:33] Nathan Wrigley: Yeah. Any more before we move on?
[00:21:35] Jessica Lyschik: I think these are like the most, absolutely the low hanging fruit is also if you use any images to add an alternative text. I think this is probably the most common one people already know. It is so easy. And even WordPress, even if you use classic themes, it’s already in the media library, the alternative text field. For block themes you have it directly at the image so it’s already in front of you. You just need to use it.
[00:21:57] Nathan Wrigley: Yeah, you just not ignore it basically. Yeah, that’s true.
So has this become kind of a habit for you then, over the last period of time since you’ve taken more and more interest in this? Have you got to the point now where this is just how it works? You know, in the same way that I drive a car and I use the gears and that’s all just second nature. Is it like that for you when you are building your themes? Because it’s now locked away in your head. Every time you do a thing that previously you would’ve omitted. You are now just in the habit. Has that been a difficult journey or fairly straightforward?
[00:22:28] Jessica Lyschik: I think it’s, like starting out with this, it would feel like a bumpy road. But for me it was, it’s a gradual process. But right now it’s really like, yeah, I just know that when I use a button in a context that is not like sending off a form to add an aria label to it, it’s like, it is baked into my brain essentially already because I know.
And I just had a very interesting example this week at work where there was a client reaching out saying, hey, we did an accessibility test on our website and it marked like two buttons that did not say what they’re doing. These were essentially missing the aria label because they had only icons on the buttons, not real text.
So if there’s just an icon, the screen reader cannot read, what is this button for, essentially, with just an icon? The win here was just to add the aria labels, because the fields were already there. This was also part of the Greyd.Suite, so from our product so I knew how to put it in there. And then it was like, oh no, like I have to do this 12 times, my colleague said. And I was like, yeah, okay, then you have to do it twice, 12 times. So 24 times. But be happy it’s not 200 times you have to do it.
So, and I said, do not take this personally. This is a great example of why putting accessibility at the very beginning of when you’re creating this makes life so much easier than rather when you just build a website and then you figure out you have to change 300 buttons. This is probably a crazy number, but just to give you an example, to change all the buttons manually again, going through every single page or whatever you have when you just could have taken the extra step, added the aria label, and then just be done with it.
[00:24:09] Nathan Wrigley: Right. That’s an interesting thought. And also the exasperation of your colleague there kind of perfectly sums up the problem. In that you see it as a problem. Does that mean I’ve got to do something 24 times? And there’s this sense of, ugh, I’ve got to do this work. And it feels like a chore. But then I suppose if you step back and look at what you’ll actually enable by doing those 24 things.
And I know that in the workday that’s hard to do. It’s hard to sort of step back and say, okay, if I do this thing 24 times, this will be the result, and lots more people will be able to, in this case, view the image.
[00:24:42] Jessica Lyschik: I mean this was like they started already working on. If you fix it now, you do not have to do it for the coming pages. So if you multiply that with how many pages more you need to do, once you get this one fixed, and ideally you need to change the aria label of the text changes obviously, but this was, I think for a header, in a header, where there was like, I think one sort of popover or popup. Fully accessible by the way, so don’t worry about that. And also a button to, I think for the phone numbers, like just a phone icon. And they could click on it and it would be something like that, along the lines. I don’t exactly remember what it was. But it was just like two icons in the header. And if you take that header, use it on, I don’t know, another 250 sites, you don’t need to do the work anymore.
[00:25:29] Nathan Wrigley: Okay. So you are painting a picture in which, get it right at the beginning, follow the guidelines, do the hard work once, then almost the career from then, from this moment forward, your life will be immeasurably easier if you build it into the theme or.
[00:25:45] Jessica Lyschik: And accessibility will not be taken as, ugh, and I now have to do this all. Because when you do it from the start, you have to make sure at the end of course that it still works. You may have to run into issues and redo stuff. That can happen. But I think you just have saved yourself so much work in the end if that requirement for some reason pops up later or so.
[00:26:10] Nathan Wrigley: I’m wondering, depending on the kind of nature of where you work, and how you do this. You know, if you’re a freelance, then this is on you. If you’re in an agency, then it may be that there’s somebody, you know, maybe there’s an SEO person, there’s a design person, maybe there’s an accessibility person. But it does feel like the moral argument states everybody should have some insight. Maybe you’re not right in the weeds of it, but you should have some knowledge of what the low hanging fruit is, at least.
[00:26:38] Jessica Lyschik: Yeah it’s, what’s the right word for it? Interdisciplinary. It is like not just the developer who needs to think of accessibility. It’s like, okay, we need to because like we provide a technical structure for it. But it also needs to be for the content people who write the blog posts, the pages, whatever, for SEO people to understand that.
And I think accessibility, if you want the entire website to be accessibility, everyone who works on a website needs to know about it. That an SEO person needs to know how to create a skip link, probably not. Or how to use, maybe to use the right text. But for them, the text would be just the, using the right heading structure, for example. This is also a requirement, that you do not use an H3 and then an H6 heading in your content, but you structure it correctly that you have the H1 on the top, and then every next level is H H2, and then every level under that is H3. So this way. They should know about this. But they do not need to know too much about the technical side. Because in the end, it all comes together and creates an accessible website.
[00:27:42] Nathan Wrigley: In your commentary a few minutes ago, you mentioned that there were some guidelines in order to put a theme on wordpress.org. Is that the nature of it? Is it a guideline, or are there some hard and fast rules, which will prevent a theme getting into the repo based upon a lack of accessibility? What I’m asking is, are there some things that you must do as of now, or is it very much, okay, if you do this, great, but if you don’t, we’ll let your theme pass anyway?
[00:28:09] Jessica Lyschik: Yeah. Let me explain this. So there’s this accessibility ready tag. So you have different tags for the themes in the repository. And in order to get the accessibility ready tag, you need to follow the requirements, the accessibility ready requirements, I think it’s completely called.
And these are as of now 18 requirements. I went through them all in my talk. We’ve already touched on some of these. Some are really low hanging fruit, some are, one of the newer ones are, a theme should not recommend or require a plugin that is not accessible. This is something else that the team came up with, which is an interesting one. There’s, I guess a lot of room for discussion.
But also another one is to have an accessibility.txt file in your theme. Which basically, it’s not a standard yet, but like close to a standard sort of, has information about what has been done in terms of accessibility. Are there any classes that you can, CSS classes that you can use to make use of texts for screen readers? So basically hide them visually, or hide these texts or items visually, but still have them read out by screen readers. So they’re not like discipline none where you just remove that basically from the accessibility tree, but make it still readable for screen readers. And just some more information about that.
Yeah, you need to meet all these requirements with your theme if you want this tag. But you can still like do not care about accessibility and still get your theme in the repo if you want.
[00:29:40] Nathan Wrigley: Would you like that to be flipped? Would you like that to be, because I mean we’re a very open ecosystem, aren’t we? And would you like to see though a day where you don’t meet these 18 guidelines, you don’t get the tag, you don’t get to play, you’re not allowed in the repo? Or is that a touch too far?
[00:29:56] Jessica Lyschik: Let me share some numbers, I think. So there are like 14,700 plus themes in the repository right now. All themes. At least that’s the number I can access. I don’t know if there’s maybe a bit more, I don’t know. But this is the public number you can access. And out of these themes, I think if I saw the correct number, it’s like just 270 have the accessibility ready tag. So then that is like 1.5% of all themes who have that tag.
So I think it will be extremely hard to force sort of, if you want to flip that, force that onto people. And I think we need to do a more gradual way. And that’s what I’m sharing my knowledge because I think it is not that hard. If you can improve the documentation for it, it will be even easier for people. And I think this is the way to go instead of forcing like, because we do not like to be forced to things we do not understand.
[00:30:50] Nathan Wrigley: That’s right. Yeah, that’s interesting. I wonder if there’s a future in which that slowly gets ramped up.
[00:30:56] Jessica Lyschik: I think with the AI agents, we will have an acceleration on this, I guess. So maybe not in WordPress themes, in the repository directly, but I think the attention will be put there and then like, oh, maybe we should make it more accessible. Let’s read into this. And I think these guidelines are also very interesting, maybe not just for WordPress themes. I mean, of course they’re for the repository, but you of course can apply them to your own custom theme, definitely. You do not have an absolute check like the team will do for you. But nothing stops you from using them even on a non WordPress site.
[00:31:30] Nathan Wrigley: Do the guidelines, do they feel like they’re kind of firmly fixed or is it always a movable feast?
[00:31:35] Jessica Lyschik: They’re relatively fixed.
[00:31:37] Nathan Wrigley: Okay, so if you were to swat up, for want of a better word, on what there is right now, there’s a good chance that the rug will not be pulled out from under you in six months, a year, two years time.
[00:31:46] Jessica Lyschik: No, I think the last time the requirements got updated was in 2012, 14. I would need to ask, Joe Dolson did the initial, or was working on the initial thing. And so it has been a while since this got updated and they just got updated last month. So I don’t think that they will be changing anything.
The one I talked about, not requiring or recommending plugins is the one, this is something, it kind of creates a grey area sort of. And I think this will be put to discussion. It’s like, I don’t mind, but I can see many people like really, not raging against it, but like raising questions about it. If this is something that should be a requirement.
But I think for like the actual technical stuff, I don’t think that there’s much that should change, because like they’re based on the WCAG requirements. These are like the standard requirements that also have, I’m not sure if they’re used on governmental things, like on the European Accessibility Act, but I think they’re a sort of base for that. And it’s not like completely this. So the theme requirements are not like the WCAG requirements 100%, but like a subset of it, sort of.
[00:32:57] Nathan Wrigley: Yeah, it’s a fairly slow moving ship in other words. If you acquire the knowledge today, you’ve got a good chance that in a year, two years, maybe even five years, the knowledge that you’ve got will need amending. But most of it will broadly work several years from now.
[00:33:11] Jessica Lyschik: It’s with like development in general. So like you always need to be constantly learning. And I think if you learn about accessibility today, I think you’re in a very good spot. Because like of course we have European Accessibility Act and governmental requirements, at least in Europe we do have them. But I think there’s already so much information out there, that it should be relatively easy to onboard you. And I think this is just beneficial if you learn, it’s basically about learning about how to use things correctly. And if you’ve got that, then you’re absolutely good to go.
[00:33:45] Nathan Wrigley: So not that long ago I suppose, we had block themes coming around, which is an entirely different way of creating themes in WordPress. So you’ve got classic themes, which is the way it always used to be. And now we’ve got block themes. Is there a striking fundamental difference in the way that you might approach accessibility if you were used to doing block themes? Is there a whole lot more to learn? Maybe it’s more straightforward if you’re using block themes. Just tell us about how those two things differ.
[00:34:08] Jessica Lyschik: Yeah. It is more straightforward actually. Core is handling stuff for you. So accessibility just got a tad bit easier if you use block themes actually. In classic themes, you have to do a lot of things manually. You have to make sure that the elements are right, that the skip link is there, for example, things that we touched on already. And in block themes, if you use the correct blocks on the correct structure, Core handles stuff for you.
For example, there’s a requirement labelled form fields. So when you use a form or the form fields should have a label to it. In themes you don’t really have that because usually you should not put like, something like a form in there. There are two forms that by default come with a theme that are the comments form, but that’s completely handled by Core. And there’s the search form on the search results page.
But in block themes, both of them are handled by Core. Both of them are accessible because Core handles it all for you. You just need to place them and actually not do anything to them. It is that straightforward.
And same for like template parts. If you want to use header and footer, just use the template parts and use them. You can assign them a header template part as header of course, and one as footer. And then the HTML text will be automatically added correctly for you. So there’s not too much that you need to do manually anymore, just get that right.
And as I say, I really love block themes for the much easier accessibility, or the way you can make a block theme accessible. This is so much easier than with a classic theme.
[00:35:38] Nathan Wrigley: So presumably though, it sounds like there’s meta knowledge, if you know what I mean. You’ve got to know which block to put in which spot, and which block wraps this other block, and the parents and the children. But if you learn that, and if you make that, we were talking about habits earlier, if you make that your habit, and then save that habit and save the theme and what have you, you are painting a picture where it’s significantly more straightforward because you don’t have to think about it in many cases. Well, that’s the wrong way of phrasing it. You don’t have to do that hard work.
[00:36:07] Jessica Lyschik: Exactly. If you have like a, sorry to interrupt you here, but if you have a theme that already gives you the correct examples, you can build off from that theme. For example, if you’re creating a new template, you can use an existing template and then just adjust it to what you need. If you need to change like colours or something but you have the structure already correct. You do not need to think about doing the structure again and maybe just have a check that it’s actually the right one. But if you just copy what’s already there, that is part of the theme, that’s actually super easy.
[00:36:38] Nathan Wrigley: I’m going to link to your presentation, which I know by the time that this goes out will be probably on wordpress.tv, I would’ve thought by that point. But I’ll link to your presentation and all of the different bits and pieces.
But I’m curious, who in the WordPress space, and maybe not the WordPress space, maybe outside of that, who do you follow or try to get guidance from? Maybe that’s a YouTube channel or a blog, or a, I don’t know, government based website. Maybe it’s just wordpress.org, I don’t know. Where do you go to swat up on all of this?
[00:37:06] Jessica Lyschik: Ooh, there are some very good resources out there. So I do follow like people within the WordPress community. I mentioned a few names already, like Joe Dolson, Rian Rietveld, Amber Hinds from Equalize Digital. They do a lot of stuff in that area. And then I also follow Sara Soueidan, she’s a developer from, I think Lebanon, if I remember correctly. She does great stuff on accessibility. There is a few more names. There are some good resources out there. I can probably research that for you because I cannot remember the names right now.
[00:37:39] Nathan Wrigley: I’m putting you on the spot. I’m sorry.
[00:37:40] Jessica Lyschik: Put me on the spot. That’s okay. I’ll share some links with you that you can then put in with the podcast information. There are some great resources both within the WordPress community but also outside of it that can give you a very good overview. And I think it’s just interesting to follow people who like can build the bridge between, okay, this is a requirement, this is how you technically do it, and this is why you do it.
[00:38:05] Nathan Wrigley: I have a friend who’s recently been on the journey of trying to go from zero to really quite proficient in this space. He’s found a bunch of YouTube channels and several of the names that you mentioned there, particularly the Lebanese lady that you mentioned.
And I think followed a course that they put together and found that structure profoundly helpful. The dry documentation, I think was the way it was described on the WCAG website can sometimes I think be a, you know, it’s hard to get into that in some way.
You know, if this all sounds like a lot of work, there’s definitely resources out there, which, fun is perhaps the wrong word, but make it more engaging. There’s videos to watch, and channels to follow and blogs to read and all of this. And so it turns this, I’m doing air quotes, dry subject into something a little bit more manageable and easy to take in.
[00:38:52] Jessica Lyschik: Yes. Yes, because like the WCAG requirements, like they’re hard to read. It’s like reading, the HTML 5 spec. This is also super hard to read.
[00:39:01] Nathan Wrigley: Yeah, it’s the cure for insomnia.
[00:39:03] Jessica Lyschik: Yeah, sort of. And it’s, yeah, I think if we have, not more content, but the right content available to people in the right spot, I think this will be beneficial for everyone.
[00:39:14] Nathan Wrigley: Yeah. I think unless there’s something else you want to cover off, I think, Jessica, I’ve asked everything I wish to. Is there anything you think we’ve omitted or are you happy to call it a day there?
[00:39:24] Jessica Lyschik: I think we’re, I mean we could go on probably for days. But I think for now it’s, we’ve covered every topic.
[00:39:32] Nathan Wrigley: Well in which case, what I’ll do, dear listener, if you go to the WP Tavern website and search for Jessica’s post, I’m not sure what number it will be as we’re recording it, go there and anything that we discussed, and any names that we discussed and those kind of things, I’ll put a link and obviously if Jessica supplies any other things she mentioned, we’ll add those in as well.
So Jessica, thank you so much for chatting to me today. And now that your presentation is done, you can relax and enjoy the rest of the spectacle.
[00:39:55] Jessica Lyschik: Yes. Thank you so much, and thanks for having me.
[00:39:57] Nathan Wrigley: You’re welcome.
On the podcast today we have Jessica Lyschik.
Jessica is a longtime member of the WordPress community who has been working in the ecosystem since 2015. She has spent years learning and advocating for web accessibility, both as a developer and as an active community participant, joining agencies, working on theme reviews, and helping to improve standards.
Many theme creators assume that making themes accessible is an intimidating task, but Jessica’s here to show you that achieving an accessibility-ready WordPress theme is more straightforward than you might imagine. Her WordCamp Europe 2026 presentation, “Accessibility in themes: easier than you think,” aimed to demystify the requirements for accessible themes, explaining what the WordPress guidelines mean in practice, where the low-hanging fruit is, and how both block and classic themes can reach accessibility-ready status with manageable effort.
We talk about the personal and moral journey that brings developers to accessibility, the technical hurdles and documentation challenges, and the ways in which things like AI agents are putting accessibility in the spotlight for everyone. Jessica talks about practical steps that quickly improve accessibility, like using correct HTML tags, adding alternative text to images, and configuring skip-to-content links, and shares why building accessibility in from the start saves time and effort down the road.
We also explore the differences, and possible advantages, of block themes when it comes to accessibility, why theme guidelines work the way they do, and the importance of interdisciplinary awareness across SEO, design, and content teams. Jessica mentions helpful resources, influential leaders in accessibility, and the ongoing need for documentation improvements to help everyone level up.
If you’ve ever felt overwhelmed by accessibility requirements, or wonder why they matter, and how you can build better WordPress sites that work for everyone, this episode is for you.
Useful links
Accessibility in themes: easier than you think – Jessica’s presentation at WordCamp Europe 2026
Accessibility Handbook – Theme section
European Accessibility Act (EAA)
What I learned at UX Scotland 2026
UX Scotland is an annual two-day conference for people working in user-centred design. This year, I went along to the John McIntyre Centre to hear about the latest developments in UX. In this post, I’ll write about my highlights from the conference.
Object-oriented UX in action: rebuilding a public sector website with structured content
Joey Gartin presenting at UX Scotland 2026. Weird slide colours courtesy of my phone.
The challenge: dividing up content and naming groupings
Out of all the talks I saw, this was the one that I found the most interesting. Joey Gartin, a content designer at Renfrewshire Council, told a story about a multiyear project to redesign the council’s website. It started with a familiar situation: the council had a large website that people found confusing and hard to use. Users couldn’t find things, and when they could, it wasn’t always easy to understand.
Renfrewshire Council needed to work out a better way to divide up and group the content on their website. Then they needed to name those groups in a way that made sense to people.
I enjoyed hearing about this because this is one of those problems that never seems to go away. When we work with digital content, whether that’s designing a homepage or tidying up a shared set of folders and files, we’re constantly looking for ways to group things. Then we’re also constantly looking for names for those groups that will make sense to people.
OOUX involves favouring nouns over verbs
Renfrewshire Council approached the problem using methods from Object-Oriented User Experience (OOUX). This is an approach to digital product design that focuses on establishing the things (or ‘objects’) that matter to your users. The approach emphasises the importance of working out the nouns involved in your service before you move on to the verbs. I’d read a bit about it a while ago on Duncan Stephen’s blog:
Duncan Stephen writes about how the Scottish Government have used OOUX approaches
The argument in favour of focusing on nouns is that this approach is more closely aligned to how people think. When you walk around a supermarket, you have a shopping list of objects. To reflect this, a supermarket is typically organised into sections that reflect broader groupings of those objects: Fruit, Vegetables, Pasta, Cake, and so on.
In a similar way – the theory goes – people often approach websites with a list of nouns in mind. They are therefore scanning webpages for keywords that match these nouns.
But many council websites use a hybrid of verb-based groupings and noun-based groupings. So you get sections called Pay, Apply, Report and Request forming a core part of their information architecture. Here are two examples.
The City of Edinburgh Council:
![]()
![]()
Renfrewshire have not adopted this model. While their page titles often start with verbs, the groupings for these pages overwhelmingly use nouns:
![]()
Joey cited the City of Sydney as another public body using this approach:
![]()
OOUX helped Renfrewshire Council to create templates
With your objects figured out, the next step of an OOUX approach is to work out:
- the relationships between objects
- the calls to action that objects offer users
- the attributes that make up objects
Joey talked us through this work. He also talked about how Renfrewshire Council used this as a foundation to create templated designs for common page types.
For example, take these two pages, both categorised as ‘service requests’:
Because they’re both service requests, you can see common sections on both pages.
For example, on the ‘Report a housing repair’ page, you have sections called:
- Before you report a repair
- How to report a repair
And on the ‘Graffiti’ page, you have:
- Before you report it
- How to report it
Joey showed us how this works behind the scenes. Renfrewshire Council use custom content types in Drupal to help structure the content writing process. So if you’re a content editor writing a service request page, you’ll be prompted to add a section on ‘Before you report it’. This helps content writers know what they need to include in a page. It also brings consistency to the website, which ultimately benefits users.
My reflections on how templates could work at Edinburgh
At Edinburgh, we use content types in our Drupal-based CMS EdWeb to create News and Event pages. So it was interesting to see another public sector website using a more extensive set of content types in Drupal. It made me reflect on how this approach might work for us. The context is so different: at Renfrewshire, it sounded like they had a more centralised approach to content management. The bulk of Edinburgh’s content publishing model is more devolved, which makes templated approaches to content more challenging. But there are clearly benefits available when you can make it work.
So lots to chew on from this talk, and it was a fun presentation to boot.
Other highlights
Sara Wachter-Boettcher on burnout
Sara Wachter-Boettcher’s keynote, “You don’t need more grit: breaking the burnout cycle in UX” was a run through of how and why burnout affects designers working in tech. It was a useful reminder to appreciate the limits of our influence within an organisation, and to be careful not to attach too much of ourselves to our job. It was cool seeing Sara in person. Her book Content Everywhere was one of the first things I read when I started in my role, and I thought it was really good.
Craig Abbott on AI and accessibility
Craig Abbott spoke about the risks and opportunities of using large language models for website design and fixing accessibility issues. One point that stood out was that LLMs are trained on some pretty ropey data. WebAIM estimate that 95% of the top million websites have detectable WCAG 2.2 failures, and these are the kinds of site that LLMs are trained on. So if you ask an AI to create a website, it will often produce something that superficially looks ok but is packed with accessibility problems.
The WebAIM Million: The 2026 report on the accessibility of the top 1,000,000 home pages
Craig showed us an example of a website he’d quickly created with AI and talked through the accessibility problems. He also showed us his other experiments. He’d had inconsistent results using AI to detect heading level failures or write alt text that took the context of an image into account. But he’d had some successes with using AI to complete more technical tasks with testable results.
James Chudley on digital sustainability
James Chudley presented on bringing sustainability practices into digital design. The highlight for me was seeing his experiments with visualising page weight across a website. Taking inspiration from an infographic using colour bars to illustrate rising global temperatures, James had applied a similar idea to visualising where a website is using more energy-intensive design choices.
James has posted his slides here:
James Chudley: Presenting ‘Beyond human centred design’ at UX Scotland
Another great conference
UX Scotland was a good chance to hear from some leading lights in the field, catch up with people and hear about some case studies that are relevant to us at Edinburgh. The two days were well organised and it gave me a lot to think about as we continue to support UX and content work at the University.
Colour System – light and dark mode colour combinations
-
Website and Communications Blog
- Videos and images – when do they add value and not just page weight?
Videos and images – when do they add value and not just page weight?
The carbon cost of using images and videos on a webpage often goes unnoticed but cumulatively can add up. Dono Abdurahmanova and I have presented at both the UCISA digital sustainability conference and the Green Software Foundation Scotland meet up in the last week or so on the topic of sustainable media use.
The key theme of the talk was around intentional use of media and our efforts to shift the narrative around the perceived necessity for videos and images to create effective content. We also shared how we’ve been working with web publishers at the University to quantify the impact of their media content. You can read more about this aspect of the work in Dono’s blog.
Do students actually watch videos on websites?
We finished by highlighting some steps you can take to make your images and videos more sustainable, if you decide they are the right medium to communicate your message.
The environmental cost of media use
Media is and will continue to be a key part of digital content strategies, that is a given and it undoubtedly does have its place as an effective communication tool – although the environmental impact cannot be underestimated.
Every page view, video stream and file download consumes energy and generates emissions. This is a fact which often goes unnoticed, as it’s not visible or as well known as other types of day-to-day activities which everyone knows create emissions.
When talking about the ‘weight’ of a web page (as I do in the title of this blog) this refers to the cumulative size of the files that are needed to load a webpage, such as images, videos, text, scripts, etc. These elements add weight to the page and the heavier the page, the greater the estimated CO2 emissions generated.
Here are a few statistics around the environmental impact of media use which provide a bit of context around why we felt it was important to think of ways to raise awareness about digital sustainability.
Digital content generally
When thinking about digital content generally, on average digital content consumption emits around 229kg of CO2 per person per year, which is up to 4% of our individual carbon footprint.
Transition Templates AI & Digital: Pathways to Net Zero+ Dr Joanna Boehnert
Webpages
When it comes to webpages – globally the average web page produces approximately 0.36g of CO2 equivalent per page view. For a site with 10,000 monthly views, that is 43kg of CO2 equivalent per year.
Website Carbon
Calculator v4 | What’s your site’s carbon footprint?
Images and videos
Then drilling down further into images and videos – streaming one hour of video content generates approximately 55g of CO2 equivalent.
Carbon impact of video streaming | The Carbon Trust
Despite their environmental impact, images make up between 49-58% of the total size of an average web page.
The starting point is to consider the value of the image or video
Often the messaging around digital sustainability can be dominated by talk of optimisation, compression and technical aspects like images formats and file sizes. However, this is actually a step ahead of where the starting point should be, which is whether the image or video adds value to the user in the first place. This is a principle which is also included in the Institute for Sustainable IT – Handbook of Sustainable Design for Digital Services.
When considering the value of media, it can be helpful to ask the following questions:
- Does it enhance clarity, context or understanding?
- Could you convey the same information without it?
While the answers will be context specific, often you can still provide the user with effective, useful information without it.
Intentional rather than automatic use of media is often not only better for the environment but also your engagement too, as it can reduce the cognitive load for the user and will likely resonate more with your audiences when used in targeted ways rather than in abundance.
“The process of behaviour change starts with awareness”
This is a quote taken from James Clear, author of Atomic Habits, which refers to the fact that people can’t change their habits if they aren’t aware of them in the first place. To this end we’ve been trying to spread the word about digital sustainability and in particular the impact of using images and videos. In doing so encouraging people to rethink their habits in relation to media use.
We’ve done this through reshaping our image guidance for the central content management system and also including the topic in our Content Improvement Clubs.
Reshaping image guidance
Working with the EdWeb service team, we reshaped the ‘Sourcing the right image’ guidance page for EdWeb 2, our central content management system. The page was heavily focused on where to find images and which were the best images to use, as these are often the first questions asked, based on an assumption that images are a necessary part of creating content.
We shifted the emphasis and tone of the page, so that it focused first on considering whether you need to use an image, highlighting the importance of both digital sustainability and accessibility when making this decision. After this we included the guidance to follow if an image is required and how to source one.
We hope that this change in approach helps to reframe the messaging and thinking around image use and encourages more intentional use of images.
You can find the new guidance on the EdWeb 2 hub.
Best practice for image use (University login required)
Including digital sustainability in our Content Improvement Clubs
Each month the UX Service runs Content Improvement Club sessions for anybody within the University who works with content. It’s a chance for them to meet up with other publishers and learn more about content design. At the beginning of the year, we ran a session on ‘5 top tips for improving your content in 2026’ and we made one of the top tips effective image use.
As part of the session, we invited attendees to look at the various different images from across the University web estate and think about which of them added value and what that value was. It was an interesting exercise and once people started to apply their mind to the question, they soon realised that some images added more value than others.
For example, having a stock image of a beach for an internal staff pensions guidance page was deemed to be more decorative, rather than aiding understanding, or helping users complete their task. Whereas the images of students on campus tours, or using University facilities, had more value in attracting prospective students by giving a human feel to events and give an idea of life at the University.
A slide from our training session on evaluating the effectiveness of different images from the University web estate.
Tips for sustainable image use
If you decide images are the right medium to communicate your message – here are some tips on how you can make them more sustainable.
- Avoid generic stock images – eye tracking studies show that people tend to ignore large or generic images. Using real-life images of people interacting with services or buildings, which are relevant to the objectives of your content is likely to increase their value / impact and make them a more worthwhile addition to the page.
- Consider the format of your image – there are various optimisation and compression tools that can help you to reduce the file size of images, without impacting on quality. At the University, we use the WebP format for images in our central content management system which results in files being 25% to 34% smaller than JPEGs.
- Consider implementing an image upload size – this can help to reduce the usage of energy-intensive large files. At the University, we’ve implemented an image upload size of 1MB for the central content management system.
Make sure that images are accessible
Whilst the focus of this blog is on sustainability, as online content grows, accessibility becomes increasingly important.
When adding an image into your content, including alternative text (‘alt text’) ensures that more users can access the information it provides. Assistive technologies such as screen readers rely on alt text to convert content (such as text, buttons, images and other screen elements) into speech or braille. This allows blind or partially sighted users to access the same information as sighted users.
You can read more about how to write good alt text in my colleague Mel Batcharj’s blog.
How to write good alt text – what we covered in our March Content Improvement Club session
Tips for sustainable video use
- Disabling autoplay – this is a simple yet impactful action that can reduce energy consumption and lower the data demand. Autoplay adds unnecessary weight to the page, causing videos to load and stream regardless of whether the user has chosen to engage with it.
- Including a written summary and transcript – this can support users who prefer reading as well as making your content more accessible. Both summaries and transcripts can help users get the key information they need and reduce the likelihood of them loading a video only to abandon it partway through as it didn’t meet their needs.
- Keep videos short and well signposted – we’ve seen from our research that user attention spans are shrinking, particularly when they are task-focused, looking to find the information they need. Therefore limiting the length of videos could help with engagement as well as sustainability. In addition using timestamps or chapter markers means that people don’t necessarily need to watch the whole video, they can skip to the relevant sections, reducing the amount of time the video is playing for, therefore reducing the energy usage.
- Avoid repetition of information – try not to repeat the same information in the video as you already cover on the webpage. If you notice that think about whether you need the video – what extra value is it adding, that the text on the page doesn’t already offer.
- Think about alternative formats – rather than video could audio files, or podcasts work? Can you communicate your message without the video? Where audio adds value but visuals are not needed, consider using the MP4 audio format instead. Audio files are significantly smaller, require less energy to stream, and can carry the same content at a fraction of the environmental cost.
Why Ghost Buttons are the Ultimate Conversion Killer
-
Webdesigner Depot
- 10 Ways to Reduce Cognitive Load Without Turning Your UI Into a Minimalist Ghost Town
10 Ways to Reduce Cognitive Load Without Turning Your UI Into a Minimalist Ghost Town
#212 – Anne Bovelett on How Web Accessibility Boosts Traffic, SEO, and Revenue
Transcript
[00:00:19] Nathan Wrigley: Welcome to the Jukebox Podcast from WP Tavern. My name is Nathan Wrigley.
[00:00:26] Jukebox is a podcast which is dedicated to all things WordPress, the people, the events, the plugins, the blocks, the themes, and in this case how web accessibility boosts traffic, SEO, and revenue.
[00:00:39] If you’d like to subscribe to the podcast, you can do that by searching for WP Tavern in your podcast player of choice, or by going to wptavern.com/feed/podcast, and you can copy that URL into most podcast players.
[00:00:56] If you have a topic that you’d like us to feature on the podcast, I’m keen to hear from you and hopefully get you or your idea featured on the show. Head to wptavern.com/contact/jukebox and use the form there.
[00:01:13] So on the podcast today we have Anne Bovelett.
[00:01:16] Anne is a seasoned accessibility strategist with many years of experience in the tech industry. Her journey into accessible design began several years ago, and since then, she’s become a passionate advocate for making the web a more inclusive place. Especially for WordPress users and developers. Drawing from her background in consulting, training, and her own experiences, Anne’s work focuses on the intersection of accessibility, universal design, and tangible business outcomes.
[00:01:46] This episode explores accessibility, not just as a moral imperative, but as a strategic advantage for website owners and businesses. Anne explains how neglecting accessibility means you are leaving serious money on the table, referencing compelling research from a variety of credible sources. These studies reveal practical data. Compliant sites enjoy increases in organic traffic, a boost in keyword rankings, stronger authority, and significant financial opportunities, sometimes running into millions and even billions.
[00:02:22] Anne talks about why accessibility hasn’t always been prioritised on the web, using analogies of the physical world, and the history of web development. She gets into the technical side as well, but this conversation is specifically geared towards the real world, bottom line, business benefits of accessible websites. Reach more users, boost revenue, and even reduce support costs.
[00:02:46] If you’re a website owner, developer, or digital business leader who’s ever wondered whether accessibility is worth it, this episode is for you.
[00:02:57] If you’re interested in finding out more, you can find all of the links in the show notes by heading to wptavern.com/podcast, where you’ll find all the other episodes as well.
[00:03:07] And so without further delay, I bring you Anne Bovelett.
[00:03:17] I am joined on the podcast by Anne Bovelett. Hello Anne.
[00:03:20] Anne Bovelett: Hi Nathan. Thank you for having me today.
[00:03:23] Nathan Wrigley: You are very welcome. Anne and I have been talking for quite a long time before we hit record and we’ve covered a lot of ground. But the ground that we’re going to cover today is all to do with accessibility, your WordPress website and why, well, why you are leaving money on the table if you are not pursuing the accessibility goals that you probably should be in the year 2026.
[00:03:43] Before we begin that, I guess it would be a good idea for you, Anne, to give us your credentials. Tell us a little bit about you and how come you get to speak authoritatively about accessibility in WordPress. So over to you, give us your bio.
[00:03:55] Anne Bovelett: It’s the most dangerous thing to ask me ever, right? Because I always talk too much.
[00:04:01] So let me do it differently this time. When I started figuring out about accessibility, about six years ago, I quickly realised that it’s not that complex to learn accessible coding. It’s not that complex to learn universal design principles. But what is hard for a lot of people working in accessibility is that many of them have this very social way of acting. I do too. I’m in it for the right reason, I think, because I want everybody to have freedom and also the freedom to make the same mistakes that we do, but also not to be constrained in any way.
[00:04:46] And then I was speaking to accessibility specialists, remediators, and in every layer of businesses, and I realised that they were being punched upon by organisations because they were just getting too many roles in one. The expectations were insane. So companies were 2 – 3000 people working for them, outputting I don’t know what kinds of digital products and websites, would expect one person to be the accessibility person to guard the compliance. And I mean this is a recipe for burnout 101.
[00:05:21] And one thing I don’t have a lack of is a big mouth. And one of the reasons why I started working for myself is because of that big mouth. I was not material to be hired, even though I managed to work for 22 years in employment. I realised at some point, if I ask a good fee, for some reason people take me seriously. Have you ever noticed that, Nathan? The more money you ask for, the more serious they’re going to take you. It’s absolutely ridiculous. But that’s what’s happening.
[00:05:59] And so I was trying to find my way in accessibility, like where do I fit in best? And then I thought, I’m going to be the flag bearer and I want to teach companies. And one of the things I like to do is to beat them with their own stick. Because I don’t care why someone makes whatever product, or whatever service they have accessible, I just care that they do. So if the stick that says money works, I’ll beat that. I’ll beat with that. It’s no doubt.
[00:06:35] And that’s where my career started changing, and especially since the past one and a half years. Someone said, you should change your job title. You should turn it into Accessibility Strategist. Well, here we are. I don’t care much for titles, but apparently that pretty much describes what I do.
[00:06:57] Nathan Wrigley: It’s kind of curious to me that if you were to, I say this phrase quite a lot on this podcast because there’s a lot of introspection going on and a lot of gazing back in time. It’s kind of curious that the accessibility bit never got importance from the get-go. And I mean right back from when the internet began.
[00:07:18] There was this great promise that suddenly great swathes of information, which would’ve been hither to unavailable to an awful lot of people, would suddenly be able to be parachuted into your living room via a computer and increasingly, you know, into your hand with a mobile phone.
[00:07:34] And yet the technology developed, the browsers developed, the web design industry developed, and it never got that importance. I’m genuinely puzzled by how that occurred. How it is that we all ignored that. And it really is probably only within the last 3, 4, 5 years that this clarion call for accessibility has become mainstream. I know that there’s people that have been banging the gong probably right from the beginning, but it has been largely ignored and I find that really curious.
[00:08:07] Anne Bovelett: I think that is due to two things. First of all, because people approach this as a purely social issue that needs to be resolved, and that people can’t imagine that they have certain users, which is arrogance at its finest. But, you know, that’s another topic.
[00:08:27] The other thing is good intentions. Like they say, the road to hell is paved with good intentions, right? Because in the beginning of the internet, when things got more colour, I always say this is the point, where things got more colourful, when Google was still small, when Alta Vista was still a thing and Yahoo and you remember, and I think we had four digit or five digit numbers for ICQ members. Actually the HTML, the sites were pretty ugly, right? They were fugly, I would say. I remember we had to build with tables and stuff, and then jump through hoops to make something look the way we wanted to.
[00:09:08] But the thing is, around that time, all we had was semantic HTML. We still have that, but back then it’s all we had. And because we were using semantic HTML, it was great for screen reader users, for example, and other assistive technology. But then everybody always wants to improve. They want to do better. And there is a German word for it, and I haven’t found the equivalent for that in English. We call it verschlimmbesserung. It literally means, instead of improving it, maybe down proving it. It’s like over-engineering.
[00:09:48] So this is what happened. And then people always want to work faster and they love building tools that help others, because in a sense, we are a social species, if you like it or not. We’re just social in the wrong things often, I think as a society. And from that perspective, there’ve been developers that had a great idea, said, let’s make frameworks, and then let’s make things easier for our fellow designers and developers.
[00:10:13] And very fast, at some point, semantic HTML was not a thing anymore because people were coding with div and span. And the div and span are the chameleons, the useless chameleons if you talk about accessibility, because you can make a div look like something, but you can’t make it behave like something until you put a ton of JavaScript on it. Div is like tofu without seasoning, right?
[00:10:41] And the same is with span. And because semantic elements like a button is challenging to style for some, a lot of frameworks came that used div and span a lot. And then they’re relying on JavaScript. And then these frameworks were growing and then at some point people were like, oh, this is the biggest framework used by everybody, so it must be good. That’s like saying the opinion of the majority is the truth. Unfortunately it’s not.
[00:11:15] That is my theory. I’m saying this more often. There was this time when everybody was doing Duolingo and then making big messages on social media, look, I’m on a 682.5 day streak in Duolingo, developers, right? And I’m like, why are you telling me about your streak for that but you can’t remember 50 semantic HTML elements? That’s very much also bashing the developer, which is pretty unfair because the problem is, with accessibility is, it’s not taken into account from the beginning.
[00:11:59] Let me compare that with another situation. So our family home burnt down to the ground and we had to rebuild, and then we got the chance to improve some things because we got modern stuff. And then, because we were building this community seminar centre at the same time, we needed to think about how we’re going to build the toilets, right? And then we had to go, and here, because the architect that helped us, he was nice guy, but he didn’t think about wheelchairs, about accessibility.
[00:12:32] At that time, I wasn’t thinking about accessibility or digital accessibility at all. But I was like, what if someone comes in with a wheelchair? Or what if we have a guest that weighs over 190 kilos? Will our toilet survive that? What kind of toilet do we need? And just close your eyes and go into that little toilet room, bathroom you call it, probably, and then close your eyes and imagine, okay, I have trouble moving, I have pain, I have rheumatism. I don’t but, you know, and I’m on a stick. Where do I put my stick? Do I have a place to put that in the corner? Can I reach for the paper?
[00:13:13] All these practical things. These are decisions that you take before you even start building the room. And it’s the same thing with anything else. Digital applications, terminals, elevators. I don’t know, anything. And the thing is, the better you do it, the less people have to ask questions afterwards about, how does this work?
[00:13:39] Nathan Wrigley: Yeah, it’s kind of interesting because in the real world, I know that in the part of the world where I live, and I’ve made this comparison on different podcasts in the past. It’s so self-evident when somebody, for example, who’s using a wheelchair. It’s so self-evident when they can’t get in the building because, well, there they are at the door with some impediment. Maybe there’s three steps that are just unachievable. And it’s really obvious. There they are in the real world. You walk past and you notice it. It’s right there in front of you. Look, there’s a problem that needs to be solved.
[00:14:13] And so for the real world, the legislation in the part of the world where I am, came into effect many years ago. And so, for example, the ramps came in and all the premises that are publicly trading things must have ramps and so on and so forth.
[00:14:26] However, the internet is a different animal in that most of us are browsing in the comfort of our own home. Nobody has any idea what you are browsing. Nobody’s got any idea where it is failing for you because they’re not staring over your shoulder. And even if they were staring over their shoulder, it would be fairly hard for them to determine that, again, to use the metaphor of getting in the building, they wouldn’t see that you couldn’t get in the building even if they were watching your phone. It has to be reported by you, the user that can’t achieve the things. And so there’s this real kind of difficulty in matching it up.
[00:15:03] And also because a website kind of looks finished when it looks finished to most people, then you just put the tools away. There’s the website. It looks finished, so it is finished. We’re done. And of course, there’s this whole increasingly vocal cohort of people who, and we’ll get into them in a moment, who are not able to access these things, but they have to self-report.
[00:15:31] And who do you even report to? If I can’t access a building on my high street, let’s say the local library, I could probably even go to the police in all honesty. There’s a central place. I could go to the police, go to the council, and I could say, this must be fixed. And it, sure enough, it will be fixed. There is no equivalence here. Who would I go to to report a problem so that it will definitely be fixed.
[00:15:53] So there’s this whole sort of strange disconnect, which presents the problem of today. How do we encourage people who don’t get the self-reporting, that it’s a jolly good idea to fix the problems in advance?
[00:16:08] Anne Bovelett: Make it hurt.
[00:16:08] Nathan Wrigley: Or make it valuable, make the fix valuable. And in the scenario that you are describing today, we’re going to talk about some articles, one of which you’ve written, but also one which has been done by accessibilitychecker.org. We’re going to look into those. This is making the economic argument for doing it.
[00:16:26] Anne Bovelett: I’m sorry for interrupting you, but it was not just accessibilitychecker.org because then everybody’s going to go, oh, yeah, another accessibility site. This was Semrush. Semrush people. They did this together with accessibilitychecker.org.
[00:16:41] Nathan Wrigley: Sorry, I’m reading out the URL where I located it, so yeah. But the point being that there’s an economic imperative. And that kind of cuts through a lot, doesn’t it? You know, if you go to a business and you say to them, if we were to make this minor tweak with your business, we could increase your revenue by 0.5 of a percent. If we make these other tweaks, we can increase you by 8%, 9%, or what have you.
[00:17:04] Any business owner who hears those words is going to be curious. Okay, right, you’ve got my attention, now what? And although it kind of misses out the whole moral argument, like we should be making sites accessible just because that’s morally the right thing to do. Put that to one side. Let’s go with the economic imperative.
[00:17:23] So I will link in the show notes to anything that we mention today. So I’ll just drop that in. Go to wptavern.com, search for the episode with Anne, and all the links will be provided there, as well, I might add with a transcript of everything that we say today.
[00:17:38] Tell us the sort of headline pieces that you found curious in the accessibilitychecker.org piece, which is obviously, as you said, created by Semrush amongst others.
[00:17:47] Anne Bovelett: I’m just looking at the first page from Semrush itself. And it was interesting because they actually have an infographic on it that says, summary of findings. That’s not accessible at all, but we used it in our Hackathon project last year. But they tested 10,000 websites. And this is actually what I, and many of the people in my line of work have been waiting for, data, data, data. Because this is what companies care about. And I understand that. You know, they are responsible for people’s salaries, not just the revenue and the turnover, but also for the people that they employ, right?
[00:18:27] And so in this research it showed, after 10,000 websites, that 70% of the sites were not compliant. Well, that’s not news, right? But the thing is, they found a 23% traffic increase tied to higher compliance. 27% more keywords ranked with accessibility improvement. So this is major, but here’s the biggest one. 90% boost in authority score for compliant sites.
[00:18:59] And the thing is, when I read people, wow, we’ve been celebrating last Friday because we had a 0.5 increase in our click rates, for example. That’s another one. I’m like, that could be 10% or 15%. I’m happy to see that it now becomes clear that accessibility affects everything.
[00:19:21] And the thing is, people approach or companies approach accessibility from a technical standpoint. Like, what do we have to change technically? But accessibility is about people. It’s the same thing with all these solutions, the overlays, the whatever. They’re trying to approach it as a digital problem. But this is a human-centric problem. This is how people use the web.
[00:19:48] And now if you go back to SEO, one thing I learned a long time ago, I mean you can tell me about Google and other search engines, whatever you want, I don’t care how technical you are, their biggest customer is the people who search on the web, not the ones who pay them to show their stuff. And so this is what search engines are looking for.
[00:20:16] And now with AI, I’m having a blast because I see people writing stuff like, oh, we have to tell the AI to understand our website. But you are leaving your fate in SEO in the hands of something that is going to interpret what you are doing there.
[00:20:36] I’m not going to name the names. It would be unfair because I’m going to confront them with that before. But, there is a massive event that has a fantastic, big website. I find it hard to navigate, but that’s a personal thing. And that is a JavaScript invested monster. And just for fun of it, I just asked AI, can you find this and this and this for me on that page? And AI was like, no, I can’t. It’s rendering JavaScript. I can’t read this. What do you think that does to a screen reader or, because they’re all using the same technology to read it.
[00:21:10] Nathan Wrigley: Yeah. When I’ve done podcast episodes about accessibility in the past, we’ve often dwelled not on this side, in fact, I don’t think we’ve ever touched sort of like the SEO and traffic benefit of it. It’s always been from the point of view of, what can you do? As an engineer, as a web developer, what can you do to go in in the weeds and fix things?
[00:21:28] We are just going to brush that aside. You can find that information out. You know, go and talk to Anne, for example, if you want to learn how to do it. But the principle here is more about the SEO and therefore the traffic side of things, on the flip side of doing the work. So you imagine, the work is not done. It’s poorer in terms of SEO and poorer in terms of reach, poorer in terms of search engine ranking, poorer in terms of revenue through your e-commerce platform or what have you. And then if you do do the work, all of those things increase incrementally.
[00:21:59] And in some cases the data shows fairly substantially. And so I’m just going to drill into each of those statistics one at a time because I feel it needs a little bit of like teasing out a little bit. So the first one is, well, there’s many statistics, but the first of the three that I’m going to mention, which you already have mentioned is organic traffic.
[00:22:17] So again, this is making the assumption that the work has been done. You’ve achieved the accessibility goals, presumably, which were many. You’ve jumped through all those hoops and you’ve got this benefit on the other side. And here’s some possible benefits.
[00:22:29] Organic traffic increased by an average of 23% as a site’s accessibility compliance score increased. So can I ask you, is that one directly related to search engines then? Because it feels like it is. You know, you did the accessibility work and a byproduct of that is that you became more visible on search engines. Have I got that right?
[00:22:50] Anne Bovelett: Yeah, of course because if assistive technology can’t read your site, the search engines probably can’t either.
[00:22:59] Nathan Wrigley: Yeah. It’s kind of interesting though that you get that much of a boost. You’d think if you had improved things, you might see, I don’t know, a few percent here and there, but this figure of 23%. I mean imagine saying that to a marketing person, or the growth person inside of a company, 23% is possible. The word average in that sentence is bolded. So it’s an average of 23%. So presumably there’s a few that are lower and there’s a few that are higher, but an average increase of 23%. So I don’t ever use the phrase win-win.
[00:23:32] Anne Bovelett: It is win-win. It’s win-win on sides. Maybe that’s a little bit the dark side in me, but I go to business dinners, meetings, entrepreneur get togethers, blah, blah, blah. And then I always hear, at some point I hear people say, I don’t get it. We are paying our SEO companies so much money, and we are not getting better results. And we have had a redesign on our website. And then I look at their website like, hmm, yeah, sure.
[00:24:01] And then they will fix the site at some point, maybe they will improve the site, where the design goes, where the user flow goes. But still, it’s not ranking better, and still it’s not ranking better. And I wonder when SEO companies are going to become so smart that they’re going to tell their customer, hey customer, stop writing click here everywhere.
[00:24:25] Nathan Wrigley: That’s a great, concrete example of what you’re talking about, because I was going to drill into the next one because honestly, the next point does confuse me a little bit. Again, I’ll link to it in the show notes, but point 4, I’ll just read it here, is websites ranked for an average of 27% more organic keywords with a higher accessibility score.
[00:24:45] Can you tease that out for me? Because I’m genuinely puzzled by what that even means. I’m not sure how there’s this overlap between accessibility compliance, and the keywords and how the search engine would pick them up. So that’s me being ignorant.
[00:24:59] Anne Bovelett: I would say, set the compliance story on fire. Torch it, and throw it away because compliance is what makes people do the bare minimum. And I think, I know they had to use this term in the report because they’ve been checking it if the site is compliant. And then you will get lulled into a false sense of security when your score says, like Google does in Lighthouse, ooh, you are 97% accessible. And like, yeah, but the 3% that you say it’s not, is what’s blocking about 80% of a group of potential visitors that you are not having.
[00:25:40] But again, it’s about, in my opinion, it’s about the way things have been coded and the way things have been written. For example, what happens is buttons that aren’t buttons that are not really saying, how do you say it? It’s the same thing. It’s the read more thing again. I have to be careful that I don’t go into the rabbit hole here too much. But it’s the read more thing. It is text where links are actually named properly.
[00:26:08] And just to give you an example, I see a lot of people who try to do affiliate marketing. Let’s say food bloggers. They make humongous sites. They love using WordPress. I know that. There are tons of plugins also for food bloggers to play out the, what do you call that in English? The nutritional values of this and that. All right. And then these bloggers, people complain about it like, oh, why do they have to write their life stories and that of the spider in the corner on the ceiling before they give me the recipe? Well, that is because they’re trying to get caught in the search engines, right?
[00:26:44] And then they have all these links. Like, someone creates a great meal with a fantastic expensive pan and a pot, and I don’t know what, and they have all these articles from Amazon. And all they have is click here, click here, click here, click here. And then imagine someone who is using that. I mean I love, I have a nice little, what do you call that, extension in Chrome? I’ve been speaking German all morning. This is why my English is so rusty right now. I have this extension and it just, in a big article, if I want to know, oh, what was that tool that she was using again? I’ll go get the link list with that little extension there, or I’ll just run the screen reader and get the link list, because that’s easy for me to do. And then all I see is click here, click here, click here. So I’m not finding the link through that pan, and so I’m not buying it through her link.
[00:27:35] Affiliate websites could make so much more money if they would just do the right thing in their content. Let’s forget about the code of the theme that they chose, just the content. If that is played out correctly, and it’s not some JavaScript generated hoo-ha, which doesn’t happen in WordPress Core, they would make a lot more money.
[00:27:58] Nathan Wrigley: Because I haven’t really been following the SEO industry for a very long time, I really don’t have much intelligence around what search engines these days look for. You know, back in the day when I was building websites, there was a, almost like a playbook that you could go through. And if you did these things, you could achieve reasonable results in SEO.
[00:28:18] And that was the state of the internet 15 years ago when algorithms were less sophisticated, and people were just beginning to kind of get online and use things like Google all the time. But it sounds to me as if we’ve got to a point with search engines, as if they’re able to, I’m maybe going to overstate this, it feels like the more human you have become as a website, the more likely Google will favour you.
[00:28:48] I’m not really encapsulating that very well, but what I mean is, if you put content on there, which is human readable. If you make it obvious where to click to do the thing, rather than stop it with keywords and things which, you know, is not really in the best intentions of humans, that’s clearly done for the algorithm only, it does sound like you are saying that the search engines favour, I’m doing air quotes here, humanity.
[00:29:15] Anne Bovelett: They always have. Let me circle back to what I said before. We, as the people who use search engines, and nowadays they’re AI in whatever they do, we are the biggest customer for them. Because if we’re not there to search, to use them, they can’t sell their services to the people paying to be found.
[00:29:37] I might be, how do you say that, unorthodox in this approach, but I’ve seen it. I have a friend, Manuela van Prooijen, she’s the owner of a company called Weblish. In the Netherlands she trains people in how to set up businesses with WordPress and how to build with WordPress. And you wouldn’t expect it when someone is just focused on that, but she’s got a very broad perspective of things. And she dove into SEO in a way that I’ve never seen before. And some of the SEO experts that I know, and we know together, were like, why didn’t we ever think of that? And it had to do with structured data. And of course, everything she builds is accessible.
[00:30:24] Nathan Wrigley: Okay, so I’m going to pivot slightly. However, I think we’ve made the case that if you are endeavouring to make your website more accessible, I think by reading that piece, you will understand that there are definite benefits in terms of traffic and search engine rankings and so on. So let’s just take that one as a given.
[00:30:43] And then I’m going to move over to a piece which you yourself wrote, not that long ago actually. Almost exactly a year ago, March 4th, 2025. It’s on your website, annebovelett.eu. It’s called The E-commerce Industry’s Billion Pound Mistake. And in here you make the argument, and you bind it to money, to actual dollar terms and things like that, which is quite interesting.
[00:31:05] So I’m wondering if you’d just paint the numbers around what you were saying here, if you can remember. I know it’s a year ago now that you wrote it. But broadly speaking, what was the economic case that you were making?
[00:31:13] Anne Bovelett: It’s actually, this is based on a British report, actually. It’s called the Click Away Pound Report. It was brought in 2019. And that actually measures how much revenue people left lying on the street by not making their shops, their online shops, accessible. And the economic case is, we say in Dutch, you thief your own wallet, if you’re not doing it. And again, these are, this is data, these are numbers.
[00:31:48] So in 2016, for example, the click away pound increased by 45%. Let me just throw around some numbers, right? So in 2016, the money that people left lying on the street by not making their eshops accessible was 11.75 billion. Billion, not million, billion pounds. In 2019, that was already up to 17 billion. Really, I don’t know if they’re going to do another Click Away Pound Report again at some point, but I think we’re going to be shocked. Because since 2019, the state of the internet actually worsened because of all this technology. And it’s getting worse because of all this vibe coding voodoo, where they’re using AI that is trained on inaccessible code. But that’s another thing.
[00:32:45] So there’s another article that I have. I think it is so much money that people leave lying on the street, this is larger than the Chinese economy, that amount. It’s in an article I wrote about e-commerce in 2022, where I was criticising CMSs, including WooCommerce, who actually did a great job. Now WooCommerce Core is now accessible. And said, okay, if your system sucks, the people using your system are going to lose without being able to help it.
[00:33:18] Nathan Wrigley: If you send me the link to that piece, I will obviously add that into the show notes.
[00:33:22] Anne Bovelett: It seems I’m on the cold side of accessibility because that is something that forever stuck with me. Someone called me cold hearted, because I’m talking about the commercial side of accessibility all the time. But, you know, there was a time, this is maybe a strange segway, but there was a time where I weighed way over a hundred kilos. I was so heavy. I had trouble moving, I was in pain, I was uncomfortable. And for me, buying clothes became an uncomfortable exercise. Going into these shops, especially these nice boutique shops, with their very small cabins, you know, trying to turn around and not being able to step into a pair of pants or whatever. Just uncomfortable.
[00:34:13] But the most uncomfortable thing about it for me was that I got blatantly ignored by the ladies that were selling the clothes in the stores. And three years after that, I had lost about 37 kilos. And I came into that one store where it was very, very apparent that they really weren’t interested in talking to me at all. I came in and they immediately jumped me, both of them, the shop owner and her assistant. And I got madder and madder and madder and madder.
[00:34:49] And at some point I said, you know what? Keep your clothes, just tell me don’t you remember me? Don’t you know who I am? No, we don’t remember you. And I was like, well, here’s the picture. Oh yeah, I’ve seen you before. And you know what, the fact, at that time I was thinking, maybe it’s because you’re too busy or you are, you know, I don’t know. But the fact that you jumped me right now with the same amount of people in the place tells me something else.
[00:35:15] Now, why am I telling this story? This is how a lot of people that need assistive technology feel, and also how older people feel on the web. I mean, I don’t know about the UK, but in the Netherlands, you can’t do your taxes without a couple of apps on a phone. Well, if you jump through a million hoops, maybe you can send it in on paper still, but it’s almost impossible. If apps like that don’t work correctly, you’re putting people’s fate in someone else’s hand, because you’re working with their tax number.
[00:35:54] I don’t know in the UK, in the Netherlands, your personal tax number, never ever give that to someone. Never. Your social security number, don’t do it. And then you’re like, maybe 60, 70-year-old, and you’re right before that stage where the technology’s getting too hard for you, but apps to do these things are too difficult.
[00:36:17] There is a local tax office in the Netherlands that had a full accessibility redesign done by Level Level in Rotterdam. And for them, the support requests went down, I think by 30% or something. I couldn’t find the case on their website anymore.
[00:36:35] But this is because people are being empowered to do things by themselves. That’s what they want. And for example, in Germany, there are statistics about that. This is an article that I actually published today that, I think it says like 90% of all German users will always try to first solve something by themselves, and if it doesn’t work they’ll walk away.
[00:36:58] Nathan Wrigley: That’s one of the curious things that come out of the article. The first part of this conversation was all about SEO and what have you. We didn’t really talk much about the person experiencing the problem. It was more about search engines and maybe how you would technically fix things. But this is so interesting. In your piece, you, and I’m just going to quote it because that’s going to be the easiest way to get the information into the record.
[00:37:20] And it says, a shocking 75% of disabled customers have willingly paid more for a product from an accessible website, rather than struggle with a cheaper inaccessible one. And that kind of sums up the whole thing really for me, that if you are faced with a struggle to do something, let’s say, I dont know, you want to buy a widget and it’s $100. The calculus that you are going through is, I could spend an hour and a half trying to get that $100 widget, or I could go to this other website and pay $120 for it and be done in three minutes. Well, that’s obvious, I know which one I’m going to do, which is really interesting.
[00:38:02] Anne Bovelett: Yeah, yeah. And there’s another thing. People are always like, oh, accessibility is only for the blind. No. The people that go forgotten in that, and I have to tell you, disabilities rarely come alone, right? I’m just going to take myself as an example. I have ADHD on steroids. I’m in the spectrum. I’m old. I need two pairs of glasses, one for my computer, one for my regular stuff. I’m starting to lose my hearing in certain regions. I am the target group. If I need to go and order, and I’m B2B, right? I’m a business.
[00:38:41] I will order B2B because then I can deduct the VAT. And I have to buy hardware. And I always try to buy the best. I will go to a store, maybe, and it’s B2B and I will go online. If I can’t figure out their stuff, I’m leaving. If I need to look at a manual, a video manual, that has background music while someone is talking, but there is no subtitles, I’m gone. I can’t follow it. My brain won’t let me.
[00:39:15] Nathan Wrigley: Yeah, I mean the analogy in my head is kind of, I don’t know, you’re going into a clothes shop or something like that and you need a new pair of shoes or something, and you discover that all the shoes are in a locked cupboard in a corner. And in order to get to the shoes, you need to ask a receptionist for the key. And then they go and find the key, and then they give you the wrong key and the key doesn’t work. And then they don’t point out where the box of shoes is, so you’re completely confused.
[00:39:36] That whole thing is just avoided by going to the next shop along the street where all the shoes are right there for you to pick up and try on and what have you. You’ve made the journey easy, and it turns out that price isn’t necessarily the prime mover here, which is really interesting. I find that statistic fascinating, that people will pay accordingly if they can get what they need out of it. I mean I know it sounds like common sense, but having it painted in those stark colours is.
[00:40:04] Anne Bovelett: Yeah, yeah. This is one of the things I did want to mention as well. I have the privilege of talking to Mark Weisbrod a lot from Greyd. You know him? He’s the CEO of Greyd. I think he’s unique, especially in the world of WordPress because he’s looking at things solely from a business perspective. He’s not distracted by technical issues or whatsoever. He will get it from there. He’s someone who often says to me like, okay, I like the story now show me the data.
[00:40:39] But then at some point, I remember it was before the European Accessibility Act was coming into effect, I think. So this, we’re talking about this in 2023 or something. And then I said, I don’t get it. Why is everybody so focused on the European Accessibility Act? Look at how much money they can make by leaving people their dignity. Because that’s basically what it is by making your stuff accessible.
[00:41:06] If you get past the stupid idea that if something is accessible, it can’t look nice. I mean, go to github.com without being logged in, that’s accessible. It’s a wonderful website. And then I said, where is the common sense? Why, if I talk to the C-suite of a company in one of those business things, and I say, listen, if you would make this and this and this more accessible in your web shop, your turn over would go up by so many percent, why are they not like, we’ve got to invest this money right now?
[00:41:39] And then he said, no matter what, people will always think with their wallet today and tomorrow. They’re not thinking about next week. Only the most visionary leaders in the industries think way more. And this is something I say now, because he said, he was telling me about they were selling, in a company he worked for, they were selling solar systems. And these systems would save the buyers so much money on the long run, but it was very hard to sell them because it was in the long run.
[00:42:20] And if a CEO or a CFO, I mean I know it sounds offending, I don’t mean it that way, but in large corporations it’s to eat or to be eaten. Managers are always afraid of their managers kicking down on them and the others kicking up, and they’re always trying to defend their own spot in the business. It’s only in smaller companies that people can have more leverage. So there are always so many powers at play in a company that if you start talking to a company about, it’s for the greater good of your company, it’s the same argument as it’s for the greater good of humanity.
[00:42:59] And I’ll just give you another number for example. Based on the Click Away Pound Report, and some other data that I have, I’ve been working on building a calculator. You tell me which country your web shop is in, you tell me how much turnover you have per year and then that calculator is going to tell you how much potential revenue you are walking away from by not making it accessible. I did this for very, very big supermarket chain in Switzerland, and the outcome was you could make 0.94% more revenue. And then you’re like, yeah, less than 1%. Yeah, sure. Ah, it’s still 350 million Swiss Francs.
[00:43:43] Nathan Wrigley: Yeah. Less than 1% but still that kind of money, wow.
[00:43:47] Anne Bovelett: Yes. And then you get this perspective thing. Because I’m pretty sure the day that this knowledge seeps through to the unions of the employees of this company, the employees are going to go like, why do we have to save money, or why do we not get a raise where you don’t take the opportunity to make that much more turnover? And then someone else with other interests in the company says, yeah, but the stakeholders, you know, or the investors, this is why this is not happening. I mean, we all think common sense is the greatest good in the world. People do not have common sense, period.
[00:44:33] Nathan Wrigley: It’s that sort of invisible layer to people who don’t experience any of the accessibility problems that the industry is trying to tackle. For example, you’re fully sighted, you can use your legs and walk about and use a mouse and use regular computer and use a regular screen and your ears are working fine and all those kind of things. All of that stuff is just sort of hidden from you, and so it just somehow doesn’t drive itself to the front of your consciousness.
[00:44:56] Which is why this is so interesting because, although you said you’ve kind of been berated in the accessibility community for banging the gong about money all the time, it’s a great way to cut through, isn’t it? You can go to the CEO of a company and make the economic argument, I would imagine, much more readily than you can do with the moral argument.
[00:45:16] Anne Bovelett: I’ve been thinking about this a lot, about writing up a profile for a position in companies that I don’t think exists yet. Because normally, we call it the sheep with five legs in Dutch. It’s very hard to find that sheep with five legs. If someone is an accessibility officer in a big company, they are being banged on for compliance. If someone is working on accessibility in a lower rank, they’re getting overworked because people have so many expectations or they just don’t do things.
[00:45:52] It’s always, this person is screaming in the desert like, hey, this is happening. I’ve seen this happen, I was guiding a company with more than I think 13 or 14 development teams, over 85 people, and they didn’t talk to each other. Design, didn’t talk to development, development didn’t talk to development in other areas, because that was how the company was structured.
[00:46:18] And I think people need to be educated in two ways to have this position that doesn’t exist yet. It’s a position where you are able to kick the shins of the C-suite in a professional manner, of course, but also sit down with development, design, and content teams and make them communicate with each other in a way that works.
[00:46:48] And for that, you have to understand these processes. And normally, I’m absolutely not for people in managing positions that know the job that the people they’re managing is doing, because they very often become that, how do you say that, the driver on the carriage running in front of the horses? You know, that’s really dangerous. You shouldn’t interfere into detail level too much.
[00:47:15] But if you understand it on a detail level, from design content and development, you can get these people to talk to each other and help each other. Because there’s absolutely nothing wrong with a developer that sees a design and is like, woah, that design, the way that is made, that’s going to cause some accessibility issues. Those are issues.
[00:47:39] And normally they will just, no, no, I was asked to develop this. I’ll develop it. Instead, you need to raise a culture where people go to the designer and say, hey, I noticed this. What is your thought behind this? And they can’t. And if they had a middle person for that where they could go to and say, look, I got this, I’m not sure about it, then you would have a fantastic flow in a company to make things accessible.
[00:48:06] Because this goes through so much more. So an article that I published today is about how much money you lose in support. It’s the same thing. If a support, people doing support are not used to really listen and someone says, I’m hard of hearing, or someone says, I have dyslexia. When you’re saying, yeah, go read it, it’s on that page on our website. If this person calls you because he couldn’t find, or understand the page, and then you force this person into vulnerability by admitting that he or she has dyslexia. And that is going to leave a very bad taste in someone’s mouth. And what happens? They’re going to walk away. If you’re not some government thing that everybody needs like, I don’t know, taxes, because otherwise they’ll come and rob you.
[00:48:54] Nathan Wrigley: It is genuinely so interesting because a lot of the content that I’ve made in the past has been definitely about the ways to fix your website. So here’s the WCAG guidelines, go figure. This episode’s been really entirely different.
[00:49:07] So first of all, looking at Semrush, and the data. Just sort of painting the picture of the improvements that you can get in terms of traffic and visibility across search engines should you go down the accessibility route. But also then getting into the financial bit, which it sounds like is your thing.
[00:49:27] So I think that’s hopefully of interest to some people who perhaps have just always thought about accessibility as a, I’m a web developer, there’s another job that I’ve got to do. Well, now you’re kind of armoured with things that you could maybe even approach clients with. You know, you’ve got a website, we haven’t looked at it in a few years, you are always looking for ways to make more revenue out of your website. Well, look, I’ve got this thing in my back pocket. This is a really credible way that we can do some tweaks. I know what I need to do. There’s guidelines that I can follow. Let’s do that and see if we can improve the revenue.
[00:50:00] I think we’ve probably covered that. And so with that in mind, Anne, just before we end, I’m going to try and link to the piece that you mentioned. I’ll certainly, anything that we’ve mentioned in this podcast, I’ll try and link to in the show notes on WP Tavern. Do you just want to tell us where we can find you? I did reference your website at one point during the podcast, but do you just want to give us that again, or maybe social networks or something like that where you hang out?
[00:50:23] Anne Bovelett: If you remember how to spell my name, just put it in Google, you’ll find me everywhere. Okay. No. So it’s Anne and then Bovelett, which is B from Bernard, B-O-V-E-L-E-T-T. You can find me on LinkedIn a lot. I’m there a lot because I talk shop a lot.
[00:50:44] Very active on X, Twitter. So that’s where you find me. And don’t be afraid to approach me. Just, if you send me LinkedIn DMs, it can take a while because sometimes I get too many, and then I’m overwhelmed and, yeah. But the best thing is to send me an email. Just go to the contact page on my website.
[00:51:06] Nathan Wrigley: All that it remains for me to do is to say, Anne Bovelett, thank you for chatting to me today. That was really interesting. Thank you so much.
[00:51:12] Anne Bovelett: Thank you for having me and giving me the platform.
[00:51:13] Nathan Wrigley: You are very welcome.
On the podcast today we have Anne Bovelett.
Anne is a seasoned accessibility strategist with many years of experience in the tech industry. Her journey into accessible design began several years ago, and since then she’s become a passionate advocate for making the web a more inclusive place, especially for WordPress users and developers. Drawing from her background in consulting, training, and her own experiences, Anne’s work focuses on the intersection of accessibility, universal design, and tangible business outcomes.
This episode explores accessibility, not just as a moral imperative, but as a strategic advantage for website owners and businesses. Anne explains how neglecting accessibility means you’re leaving serious money on the table, referencing compelling research from a variety of credible sources. These studies reveal practical data. Compliant sites enjoy increases in organic traffic, a boost in keyword rankings, stronger authority, and significant financial opportunities, sometimes running into millions and even billions.
Anne talks about why accessibility hasn’t always been prioritised on the web, using analogies of the physical world and the history of web development. She gets into the technical side as well, but this conversation is specifically geared toward the real-world, bottom-line business benefits of accessible websites, reach more users, boost revenue, and even reduce support costs.
If you’re a website owner, developer, or digital business leader who’s ever wondered whether accessibility work is ‘worth it’ this episode is for you.
Useful links
Manuela van Prooijen’s Weblish
The e-commerce industry’s billion-pound mistake
Why accessibility is fundamental in 2026
At WP:26, Human Made’s virtual event exploring the future of WordPress, much of the conversation focused on what’s changing across the web. AI is accelerating workflows, enterprise platforms are becoming more complex, and expectations around digital experiences continue to rise.
But in the middle of all that change, one session brought the conversation back to something more fundamental.
In a conversation with Rian Rietveld, we explored accessibility not as a compliance exercise or a checklist, but as a core part of how we design and build for the web. It quickly became clear that while the tools and technologies around us are evolving rapidly, the question of who we are building for remains just as important as ever.
Throwing off the shackles of compliance checklists, Rian delivered a clear and focused take on how accessible design fundamentally impacts your audience reach and revenue. Across an insight-packed 30-minutes, she guided us through the current state of WordPress accessibility, the awesome WP Accessibility Knowledge Base project she’s been working on, and—crucially—the highest-return investment teams can make today.
Read on to get the key moments and insights from Rian’s session.
From compliance to commercial reality
One of the most striking themes from the session was how quickly the conversation around accessibility is shifting. What was once framed as a compliance requirement is increasingly being recognised as a commercial imperative.
Excluding users with disabilities doesn’t just create a poorer experience, it actively limits your audience. As Rian pointed out, that audience is far from marginal. In fact, the cost of getting accessibility wrong is measurable, with billions in lost revenue each year in markets like the UK alone.
For teams building on the web, this reframes the challenge. Accessibility is no longer about meeting minimum standards or ticking regulatory boxes. It is about ensuring your product is usable by as many people as possible, not only because it is the right thing to do, but because it directly impacts reach, engagement, and ultimately, revenue.
Accessibility, AI, and search are converging
One of the most interesting parts of the discussion was how accessibility is increasingly intersecting with other concerns that teams are already prioritising, particularly around AI and search.
As highlighted throughout WP:26, machines are playing a growing role in how content is discovered, interpreted, and acted upon. Whether it is search engines, assistive technologies, or AI agents, all of these systems depend on the same underlying signals to make sense of the web.
Those signals are not new. They include things like semantic HTML, clear heading structures, meaningful labels, and predictable interactions. In other words, the same practices that have always underpinned accessible design.
What is changing is the level of importance. Accessibility is no longer a separate consideration running alongside SEO or AI readiness. It is becoming part of the same foundation. If content is not structured in a way that machines can understand, it becomes harder to find, harder to interpret, and ultimately less useful.
That convergence raises the stakes. Getting accessibility right is no longer just about supporting specific users. It is about ensuring content works in an increasingly machine-mediated web.
Actionable strategy: The highest-return on investment
If advising a digital leader, Rian shared the single highest-return investment in 2026:
- Training people: Train your designers, content creators, and developers on how to build accessible products. Most accessibility is “just decent code, decent HTML.”
- Prioritise keyboard navigation: A website and all its functionality must be able to work with the keyboard only. This is the essence of accessibility and should be a non-negotiable testing priority.
- Contribute to the Knowledge Base: Rian encouraged the community to get involved with the WP Accessibility Knowledge Base to create one central source of truth for all WordPress accessibility documentation.
“If you create only for perfect people, people who have perfect eyesight, are clear of mind, can move their hands, are web savvy. Well, then you say, okay, only those people are allowed in my web shop and the rest of the people I don’t give access to and the rest of the people are quite a lot of people. So you have to take into account that you build for everyone, not only for perfect people.” – Rian Rietveld, Web Accessibility Specialist.
Ready to explore all the insights and research from WP:26? Access the full WP:26 Event Replay page here and download our supporting market analysis report, ‘WordPress in 2026: The dawn of the intelligent CMS’.
The post Why accessibility is fundamental in 2026 appeared first on Human Made.