Changelog for Mobile Accessibility at W3C

May 2024

In “W3C WAI Addresses Mobile Accessibility” section:
- Replaced “To learn how WCAG 2.0 can be applied” with “To learn how WCAG 2 can be applied”
- Replaced “WCAG2ICT: Applying WCAG 2.0 to Non-Web Information and Communications Technologies” with “WCAG2ICT: Applying WCAG 2 to Non-Web Information and Communications Technologies”
- Replaced “WCAG 2.1, published in June 2018, includes new requirements (“success criteria”) addressing mobile accessibility.” with “New requirements (“success criteria”) addressing mobile accessibility were added to WCAG 2.1 and WCAG 2.2.”
- Add a link to What’s New in WCAG 2.2

Content after update

-   To learn how WCAG 2 can be applied to mobile web content, mobile web apps, native apps, and hybrid apps using web components inside native apps, see [Mobile Accessibility: How WCAG 2.0 and Other W3C/WAI Guidelines Apply to Mobile](http://www.w3.org/TR/mobile-accessibility-mapping/).
  -   A more general resource that also includes mobile apps is [WCAG2ICT: Applying WCAG 2 to Non-Web Information and Communications Technologies](/standards-guidelines/wcag/non-web-ict/).
  -   New requirements ("success criteria") addressing mobile accessibility were added to WCAG 2.1 and WCAG 2.2. They are introduced in [[What’s New in WCAG 2.1]](/standards-guidelines/wcag/new-in-21/) and [[What’s New in WCAG 2.2]](/standards-guidelines/wcag/new-in-22/).

In “Get Involved” section:
- Updated Task Force facilitator & emails addresses.

March 2019 - May 2021

In frontmatter:
- Update translation date:
  last_updated: 2021-05-17
- After permalink, add “changelog: /standards-guidelines/mobile/changelog/”:
  permalink: /standards-guidelines/mobile/
  changelog: /standards-guidelines/mobile/changelog/
- After “path:”, add “content/” before “index”. Be careful not to change the spacing before “path”. It should be lined up with repository: above it.
  path: content/index.md
- Under “footer: >”
  - Update the first date. (Leave the translation of “Updated” and “First published January 2008”.)
  - Add “CHANGELOG.” after 2008. Leave it in all capital letters and do not translate it.
    Updated 14 May 2021. First published January 2008. CHANGELOG.
[editorial] Under “It addresses a wide range of issues:”, deleted “a” from:
device use in different settings, such as bright sunlight
In Summary box (which is after {% include box.html type="start" h="2"), in the 5th bullet (under “WAI’s Mobile Accessibility Task Force work includes:”), change “2.1” to “2” in:
WCAG 2 Success Criteria and Techniques

Note: Leave 2.1 later in the page in:
- WCAG 2.1, published in June 2018, … [What’s New in WCAG 2.1](/standards-guidelines/wcag/new-in-21/)
[editorial] Under “More than ‘Mobile’” section, changed “address” to “addresses” in:
It addresses a wide range of issues`
[editorial] Under “It addresses a wide range of issues:”, deleted “a” from:
device use in different settings, such as bright sunlight
Under “W3C WAI Addresses Mobile Accessibility”, in second sub-bullet, changed link from “https://www.w3.org/TR/wcag2ict/” to:
Tip: Can search for “ict”
[WCAG2ICT: Applying WCAG 2.0 to Non-Web Information and Communications Technologies](/standards-guidelines/wcag/non-web-ict/)
Delete paragraph:
Tip: Can search for “2019”
WAI's Education and Outreach Working Group (EOWG) is developing a **Mobile Accessibility Introduction** with guidance for designers and developers. We expect it to be completed in late 2019.
Under “## Get Involved {#involved}”, the first sentence, make sure the link has double brackets.
Tip: Can search for ‘#involved’
General information is available in [[Participating in WAI]](/about/participating/).

Thanks to Tolu Adegbite for work on May 2021 updates!