Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change "mobile devices" to "smartphones" #3776

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

patrickhlauke
Copy link
Member

@patrickhlauke patrickhlauke commented Apr 5, 2024

This removes the weird ambiguity of "why list tablets separately from mobile devices" and closes #3750


Preview | Diff

This removes the weird ambiguity of "why list tablets separately from mobile devices" and closes #3750
@bruce-usab
Copy link
Contributor

Discussed on TF call 4/12. There was not support for the change. Suggestion was made to address via Proposed response, and not a PR.

@patrickhlauke
Copy link
Member Author

patrickhlauke commented May 4, 2024

I'd still put my case forward for this. In the discussion that led to it, we seemed to agree that "mobile devices" is a loaded term - some people see it as encompassing all sorts of mobile devices (smartphones, tablets, phablets, arguably even laptops), in which case it then looks odd to make an apparent distinction between "mobile devices, and tablets"; others see mobile devices as meaning purely phones, and therefore name-checking "tablets" separately makes sense.

To satisfy both groups, the simplest way is to just avoid the loaded term "mobile devices" and to explicitly say "smartphones and tablets". Don't think anything is lost here by abandoning the ambiguous group term in favour of the actual device classes themselves.

But yes, it's a very low priority/importance thing. Mainly, it just reads odd to people. Either way, let's make a decision on this and move on, so this doesn't hang around gumming up effort that should be spent elsewhere.

guidelines/index.html Outdated Show resolved Hide resolved
Co-authored-by: Mike Gower <mikegower@gmail.com>
@@ -13,7 +13,7 @@
</head>
<body>
<section id="abstract">
<p>Web Content Accessibility Guidelines (WCAG) 2.2 covers a wide range of recommendations for making Web content more accessible. Following these guidelines will make content more accessible to a wider range of people with disabilities, including accommodations for blindness and low vision, deafness and hearing loss, limited movement, speech disabilities, photosensitivity, and combinations of these, and some accommodation for learning disabilities and cognitive limitations; but will not address every user need for people with these disabilities. These guidelines address accessibility of web content on desktops, laptops, tablets, and mobile devices. Following these guidelines will also often make Web content more usable to users in general.</p>
<p>Web Content Accessibility Guidelines (WCAG) 2.2 covers a wide range of recommendations for making Web content more accessible. Following these guidelines will make content more accessible to a wider range of people with disabilities, including accommodations for blindness and low vision, deafness and hearing loss, limited movement, speech disabilities, photosensitivity, and combinations of these, and some accommodation for learning disabilities and cognitive limitations; but will not address every user need for people with these disabilities. These guidelines address accessibility of web content regardless of device (such as desktops, laptops, and mobile devices). Following these guidelines will also often make Web content more usable to users in general.</p>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"on any" seems simpler than "regardless of". And there are a huge range of devices people use in reality that present web content, includng ATMs, information kiosks, watches, those spyng machines in your house that you talk to, TVs, etc. In addition, these things keep getting blended into each other. IMHO the less we try to list devices, the better...

Suggested change
<p>Web Content Accessibility Guidelines (WCAG) 2.2 covers a wide range of recommendations for making Web content more accessible. Following these guidelines will make content more accessible to a wider range of people with disabilities, including accommodations for blindness and low vision, deafness and hearing loss, limited movement, speech disabilities, photosensitivity, and combinations of these, and some accommodation for learning disabilities and cognitive limitations; but will not address every user need for people with these disabilities. These guidelines address accessibility of web content regardless of device (such as desktops, laptops, and mobile devices). Following these guidelines will also often make Web content more usable to users in general.</p>
<p>Web Content Accessibility Guidelines (WCAG) 2.2 covers a wide range of recommendations for making Web content more accessible. Following these guidelines will make content more accessible to a wide range of people with disabilities, including accommodations for blindness and low vision, deafness and hearing loss, limited movement, speech disabilities, photosensitivity, and combinations of these, and some accommodation for learning disabilities and cognitive limitations; but will not address every user need for people with these disabilities. These guidelines address accessibility of web content on any kind of device (including desktop snd laptop computers, mobile devices, and kiosk devices). Following these guidelines will also often make Web content more usable to users in general.</p>

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

WCAG Abstract section makes distinction between "tablets" and "mobile devices"
5 participants