6 skills.
Use when asked to add or review ARIA (Accessible Rich Internet Applications) attributes — roles, states, and properties for dynamic/interactive elements — as a supplement to semantic HTML, not a replacement for it, and grounded in web-content-accessibility-guidelines' operable/perceivable criteria.
Use when asked to communicate effectively across cultural backgrounds — cultural awareness, language differences, nonverbal communication, direct/indirect and high/low-context styles, sensitivity and adaptation — as a communication discipline, distinct from inclusive-language's specific wording focus.
Use when asked about ensuring all individuals and communities can access and effectively use digital technologies — connectivity, digital skills/literacy, accessibility, culturally appropriate content, digital citizenship and safety — as the broad societal umbrella that accessibility-testing and web-content-accessibility-guidelines address one dimension of.
Use when asked to design or document keyboard shortcuts (hotkeys) — accelerating workflow, accessibility for mobility-impaired users, consistency/standardization, customization — for a software application or operating system.
Use when asked about how screen readers work and how to design/build for them — audio representation of content, semantic markup and alt text, navigation mechanisms, structural/context cues — as the underlying assistive technology screen-reader-testing verifies against.
Use when asked about WCAG specifically — the perceivable/operable/understandable/robust (POUR) principles and A/AA/AAA conformance levels — as the formal standard accessibility-testing and screen-reader-testing verify compliance against.