Author: stevef

Original Atlas browser logo Goatse by Adrian Shat advice One of the issues that I found most peturbing from the Atlas browser FAQ’s for front end developers was the advice to use ARIA: ChatGPT Atlas uses ARIA tags[sic]—the same labels and roles that support screen readers—to interpret page structure and interactive elements. To improve compatibility, […]

There is a new browser in town: ChatGPT Atlas browser Given OpenAI’s general flakiness when it comes to UI design, accessibility and usability, I installed the browser with little enthusiasm as I felt it was going to be crap accessibility wise. But we can always hope… It is a closed source browser (I believe), using […]

Updated 24 September 2025 – repointed links to new home Below is a list of links to each of the HTML elements in the screen-reader-HTML-support tables following an element named link will display the Screen Reader HTML Support – Lookup app with the data for that element. This works due to each link having the […]

last updated 24 September 2025 Kazuhito Kidachi asked for a way to contrast and compare support across screen readers in the HTML support tables I took some time over the weekend to create a Lookup app (of sorts) What it does is take the data in the JAWS/NVDA/VoiceOver HTML support tables being published by TetraLogical […]

Let me be perfectly clear, this script was generated by ChatGPT. It came to be from a problem I encountered when QAing a WCAG 2.2 assessment. I knew that the advice provided  was not right, but didn’t know what was going on. I suspected it was something to do with aria-activedescendant implementation (in a custom […]

As part of my cycle of going through useless tasks I rechecked the web UI of our old friend ChatGPT. Given the emormous amounts of money being progressively spaffed up the wall on LLMs by the feckless impotent men children of Silicon Valley I would expect making the UI of their product accessible is a […]

Patrick muses upon his Web Standards life, from the bad side of the moon It’s a hint not a label The placeholder attribute is defined as: The placeholder attribute represents a short hint (a word or short phrase) intended to aid the user with data entry when the control has no value. A hint could be a sample value […]

When is a label also an (accessible) name, when is it not and when is it neither? WCAG definitions: label text or other component with a text alternative that is presented to a user to identify a component within web content A placeholder can be an accessible name, but can never be a label A label element can be […]

WCAG 4.1.2 Name, Role, Value, states states, properties, and values that can be set by the user can be programmatically set Non-geek speak If something a person does to a thing causes it to change then the change is reflected in the code a person can Press something – aria-pressed Check something – aria-checked Select something aria-selected […]

so so intro It is unclear to web developers, browser developers and assistive tech developers when an accessible name provided via aria-label/aria-labelledby should replace the child content as the accessible name or be announced in addition to subtree content. This results in bugs and frustration for anyone that this issue touches. Taking the ARIA in […]