Gallery

State of HTML Planning

Non-content

Explore

Survey Outline

Accessibility

Last edited 338 days ago by S G

Legend: ✅ Definitely keep 🔶 Not sure yet ❌ Likely Remove

What kind of user disabilities do you account for when designing websites?

(Format: Checkboxes with

multiple custom answers⁠

, no sentiment)

Low vision (including blindness)

Auditory disabilities (deafness, hard-of-hearing)

Motor disabilities (inability to use a mouse, limited fine motor control)

❌Disabilities causing slow response time

Atypical color vision (”color blindness”)

Vestibular disorders (e.g. epilepsy)

Learning disabilities (e.g. dyslexia, dyscalculia)

Other cognitive disabilities (e.g. ADHD)

🚫 None

⁠

What other techniques are part of your regular accessibility strategy?

(Format: Checkboxes + multiple custom options)

Improving focus order with tabindex (e.g. roving tabindex, tabindex="0" to enable focus etc) | tabindex

Intuitive keyboard navigation (besides tab order) | keyboard_navigation

ARIA (role and aria-* attributes) | aria_attributes

Providing alt text that describes the purpose or content of the image | descriptive_alt_text

Skip to content link | skip_to_content

Using <fieldset> and <legend> to group related form elements | fieldset_and_legend

Using headings (<h1> - <h6>) that correctly represent the information hierarchy | headings_hierarchy

Ensuring that link text makes sense out of context | meaningful_link_text

Ensuring every form control has a label (or aria-label etc) | form_control_label

Ensuring focus is clearly visible | visible_focus

Ensuring pointer interactions (e.g. hover) have a keyboard alternative | pointer_alternative

Ensuring sufficient color contrast | color_contrast

Ensuring that no information is conveyed by color alone | color_alternative

prefers-reduced-motion media query | prefers_reduced_motion

prefers-contrast media query | prefers_contrast

🚫 None

⁠

Which screen readers do you test in, if any?

VoiceOver | voiceover

JAWS | jaws

NVDA | nvda

🚫 None

⁠

What tools do you use for accessibility testing, if any?

(Format:

Checkboxes with sentiment chips⁠

+ multiple custom options)

Axe | axe

Lighthouse | lighthouse_a11y

Assistive labs | assistive_labs

Voiceover.js |voiceover_js

Guidepup | guidepup

Accessibility Insights

Usability testing that includes people with disabilities

🚫 None

⁠

Main features: (insert table here)

tabindex

✅ focusgroup

✅ role

❌ prefers-reduced-motion

❌ prefers-contrast

✅ landmark elements

❌ alt attribute

Feature questions

Question

Focus area

Type

Status

Discussion

Upvotes

In Part 1

ARIA

aria

Accessibility

HTML attribute

Stable

Yes

search_element

Accessibility

HTML element

Future

Yes

focusgroup attribute

focusgroup_attribute

Accessibility

Interactivity

HTML attribute

Future

Yes

Landmark elements

landmark_elements

Accessibility

HTML element

Stable

Yes

No results from filter

⁠

What are your biggest pain points around web accessibility?

(Format:

List of freeform fields⁠

)

Want to print your doc?
This is not the way.

Try clicking the ⋯ next to your doc name or using a keyboard shortcut (

CtrlP

) instead.