Techniques Of Future Past

[fstrr]

There's quite a few "potential future technique" comments in documents, some of which have been there for years. Which have the sands of time running low for them and which are the ones for you and me? If you had the time to lose, an open mind and time to choose, would you care to take a look?

Conformance

1. Expressing a conformance claim to WCAG 2.0 in Dublin Core elements
2. Providing reciprocal links between conforming and non-conforming versions
3. Excluding non-conforming content from search results
4. Using content negotiation
5. Not displaying content that relies on technologies that are not accessibility-supported when the technology is turned off or not supported.
6. Using metadata to allow location of a conforming alternative version from the URI of a non-conforming page

Concurrent input mechanisms

1. Only using high-level, input-agnostic event handlers, such as focus, blur, click, in Javascript
2. Registering event handlers for keyboard/keyboard-like and pointer inputs simultaneously in Javascript; see Example 1 in Pointer Events Level 2

Content On Hover Or Focus

1. ARIA: Using role="tooltip"
2. CSS: Using hover and focus pseudo classes
3. Failure to make content dismissable without moving pointer hover or keyboard focus
4. Failure to meet by content on hover or focus not remaining visible until dismissed or invalid

Label In Name

1. If an icon has no accompanying text, consider using its hover text as its accessible name
2. Accessible name contains the visible label text, but the words of the visible label are not in the same order as they are in the visible label text
3. Accessible name contains the visible label text, but one or more other words are interspersed in the label

Pointer Cancellation

1. Touch events are only triggered when touch is removed from a control

Reflow

1. CSS, Reflowing simple data tables
2. CSS, Fitting data cells within the width of the viewport
3. Mechanism to allow mobile view at any time
4. Alternate view supporting Reflow for otherwise excepted content
5. Using PDF/UA when creating PDFs

Accessible Authentication (Enhanced) and Accessible Authentication (Minimum)

1. Providing WebAuthn as an alternative to username/password
2. Providing a 3rd party login using OAuth
3. Using two techniques to provide 2 factor authentication

Redundant Entry

1. Not requesting the same information twice

Keyboard

1. Using WAi-ARIA role, state, and value attributes if repurposing static elements as interactive user interface components

Identify Purpose

1. Using microdata to markup user interface components

Seizures and Physical Reactions

1. Ensuring that content does not violate spatial pattern thresholds

Status Messages

1. Using role="progressbar"
2. Using aria-live regions with chat clients
3. Using role="marquee"
4. Using role="timer"
5. Using role="alert" or aria-live="assertive" on content which is not important and time-sensitive
6. Using aria-live regions to support 1.4.13 Content on Hover or Focus

[patrickhlauke]

Pointer Cancellation
Touch events are only triggered when touch is removed from a control

Throwing my hat in the ring for this, with some caveats ... I think I'd much rather turn this around into a failure technique, where things trigger on mousedown, pointerdown, touchstart rather than relying on standard click (where then it's the UA that sorts out when it's triggered) or - if you have to do it with basic principles - mouseup, pointerup, touchend

[patrickhlauke]

Ditto for this (since I happen to know one of the editors for Pointer Events grin)

Concurrent input mechanisms
Only using high-level, input-agnostic event handlers, such as focus, blur, click, in Javascript
Registering event handlers for keyboard/keyboard-like and pointer inputs simultaneously in Javascript; see Example 1 in Pointer Events Level 2

[fstrr]

I can take the status messages ones unless anyone has a burning desire to work on those.

[patrickhlauke]

I can take the status messages ones unless anyone has a burning desire to work on those.

I'll suggest a peek at https://tetralogical.com/blog/2024/05/01/why-are-my-live-regions-not-working/ for those :)