-
### Backstory:
A third party has done some testing of a number of published EPUBs currently circulating.
This company validates all incoming EPUB content against the [WCAG AA 2.2 rules](https://lin…
-
In WCAG intro we currently say:
> The success criteria are what determine “conformance” to WCAG. That is, in order to meet WCAG, the content needs to meet the success criteria.
What determines c…
-
**Description**
It is enough for user to hear the same information once upon reaching element. In this case pagination.
Especially for the users using assistive technology.
**Preconditions**
Stateful…
-
**Description**
Focus should be visible on all interactive elements.
**Preconditions**
Stateful App Search -> Engines -> Search UI -> Search Experience page is opened.
Engine is added.
**Steps to re…
-
**Description**
Elements has to be announced correctly for the user using assistive technology.
**Preconditions**
Stateful App Search -> Engines -> Search UI -> Search Experience page is opened.
Engi…
-
### Description of the bug
This is related to issue #908 where the overall issue was fixed, but with additional scenarios the focus would stop working as intended. This is related to how the HTML is …
-
We have implemented/fixed lots of accessibility-related issues over the years, but we don't have an official statement on [WCAG compliance](https://www.w3.org/TR/WCAG20/). Some users have asked whethe…
-
_From @jake-abma on June 8, 2018 15:26_
At [https://www.w3.org/TR/WCAG21/#wcag-2-layers-of-guidance](url) I see two references to WCAG 2.0.
Shouldn't this be adjusted to 2.1?
> Success Criteria…
-
In various places like https://www.w3.org/WAI/WCAG21/Understanding/conformance it still refers to 2.0. This may be due to the fact that some of the documents appear "shared" in the source folder here …
-
### Summary
Global template issue – The home page contains a group of slides and controls that are visually and functionally a carousel. These elements have not been enclosed in a labelled landmark…