HTML Accessibilitybackground I originally wrote this advice between 2010-2014 for the HTML5 specification with help from Laura Carlson and others. I still refer to it and decided it needed an update and a new home. Table of contents A link or button containing nothing but an image Graphical Representations: Charts, diagrams, graphs, maps, illustrations Images of […]
The WCAG success criterion 1.4.3: Contrast (Minimum) requires that: The visual presentation of text and images of text has a contrast ratio of at least 4.5:1 There are several exceptions to this rule, including: Text or images of text that are part of an inactive user interface component Which means in HTML that interactive elements with […]
I have noticed a number of people are advocating the use of AI/LLMs (Large Language Models) for accessibility testing and/or code remediation. My onging question is why? My personal experience with ChatGPT, for example is that it sucks at these tasks. Or it may well be that I suck at using AI to elicit useful/trustworthy […]
What is the measure of integrity in the marketing of accessibility testing tools? I would expect that while marketing bumpf extolls the virtues of a companies software, it is factual. This is not always the case. We have all witnessed the loss of trust in Accessibility Overlay companies, because their claims and the reality of what […]
In 2017 I embarked on a journey to improve and open the reporting of issues with JAWS support for Web Standards. I continued to work on this after leaving TPGi, until now… One of the resources I created and maintained while involved with the project was Jaws HTML Support. This resource provides information about how JAWS […]
Update: 01/10/2024 Several people have questioned my reasoning for writing about the use case of popover as a tooltip, no I was not on drugs, at the time of writing I noticed that GitHub was using popover as a tooltip: During preparation for my talk at State of the Browser 2024 I started to look […]
I wuz reviewing a best practice issue being developed for TetraLogical and wanted to check the verascity of a statement it contained. the information provided in the title attribute is not accessible to users navigating with a keyboard or touch devices, as they cannot hover over elements to view the content. I know this was true […]
This is a shout out to David MacDonald, who while absent of late due to family responsibilities, has been a constant presence in the W3C WAI working groups and contributing to accessibility web standards for many a year. Besides working tirelessly to improve accessibility standards he also wrote and produced the iconic song about WCAG […]
The good people of Dunnington gather around their communal tele-visual apparatus to learn of HTML usability blights from a young Dr Swallow. In 2014 I wrote an article What ARIA does not do It stated: ARIA is a set of attributes that can be added to HTML elements (and other markup languages) to communicate accessibility role, state, name […]
Self portrait of Peak WCAG Trash Panda Patrick Lauke Does WCAG 2.2 Level AA apply to Native apps? yes, mostly How/where it (non-normatively) applies is detailed in Guidance on Applying WCAG 2 to Non-Web Information and Communications Technologies (WCAG2ICT) Below is what I think is the pertinent information for Level AA criteria in an abbreviated form, which […]