Comments (12)
happy to do a PR for the above sidestep if people think it would be a satisfactory middle ground
from wcag.
Since there are folks in either camps of thinking:
a) tablets are mobile devices
b) mobile devices don't include tablets
I think its more comprehensive to call out tablets specifically so that people who think B, don't misinterpret it to mean that tablets are excluded. People who think A won't run into that risk of missing something, they'll just think its redundant.
from wcag.
also, i'd say that it's a fairly trivial thing here either way ... if as a reader somebody gets tripped up at the first sentence, they're not going to have a good time when trying to read the rest of this dense document.
from wcag.
@avkuo the convention is that items are only moved to "Drafted" when they either contain a resolution in the form of a PR or a Draft Response (where it is felt no PR is necessary).
It appears that you may be proposing your response as a draft response? The convention is that:
- it would be in the form of a comment prefaced by Proposed Working Group response
- it would not use first person language, but instead "we" language, since it is intended to be an official response from the group
- the issue would be given a label of Response-Only
Please have a look at #2973 (comment) and feel free to either make a new comment, or modify your existing comment to make it into a proposed response.
Once the working group approves a response, they will alter 'proposed' to 'approved' in the comment and the issue will be closed
from wcag.
...could also circumvent the ambiguity by changing the sentence to desktops, laptops, tablets, and smartphones.
from wcag.
Since there are folks in either camp of thinking: a) tablets are mobile devices b) mobile devices don't include tablets
It's more comprehensive to call out tablets specifically so that people who think B, don't misinterpret it to mean that tablets are excluded. People who think A won't run into that risk of missing something, they'll think its redundant.
Hi @avkuo I see your point. However, we also have camps of thinking with e-readers as mobile devices. But some of them are tablet size.
My main concern is about the device categories and why we use them. Otherwise, we might need to keep creating new categories for other devices according to the camps of thinking that can also be distinct according to the document localization.
Also, there are documents in W3C stating " Mobile devices range from small handheld devices (e.g. feature phones, smartphones) to somewhat larger tablet devices. "
Or
https://www.w3.org/WAI/standards-guidelines/mobile/#intro
“Mobile accessibility” refers to making websites and applications more accessible to people with disabilities when they are using mobile phones and other devices. WAI’s work in this area addresses accessibility issues of people using a broad range of devices to interact with the web, including:
- phones and tablets ...
Hence, we either follow what is already declared across a range of documents or recommend and review other documents that put tablets and phones under the same device category.
if as a reader somebody gets tripped up at the first sentence, they're not going to have a good time when trying to read the rest of this dense document.
Agree! I would rather to simplify the text being more generic for hardware to include any forthcoming new device instead of adding sub-categories of devices.
from wcag.
Proposed Working Group response
Since there are people in either camps of thinking:
a) tablets are mobile devices
b) mobile devices don't include tablets
We would rather call out tablets specifically in this instance to clarify for people who think mobile devices don't include tablets, that tablets aren't excluded from accessibility guidelines.
We do not believe it to be contradictory to include tablets in examples of mobile devices or mobile accessibility on other W3C pages, rather including tablets as an example is serving the same purpose (as this instance) to reaffirm people in both camps of thinking that tablets aren't excluded from accessibility considerations.
from wcag.
happy to do a PR for the above sidestep if people think it would be a satisfactory middle ground
Sorry, I'm disagreeing because I think the prior text will cover more use cases.
from wcag.
happy to do a PR for the above sidestep if people think it would be a satisfactory middle ground
Sorry, I'm disagreeing because I think the prior text will cover more use cases.
I see your point, but I still think that the prior text may cause some misunderstanding on devices creating a specific category.
W3C itself has document already stating that:
_Mobile" is a generic term for a broad range of wireless devices and applications that are easy to carry and use in a wide variety of settings, including outdoors. Mobile devices range from small handheld devices (e.g. feature phones, smartphones) to somewhat larger tablet devices. _
Source: https://www.w3.org/TR/mobile-accessibility-mapping/#h-wcag-2.0-and-mobile-content-applications
Hence, we should adjust one of the documents, since they have distinct concepts on device categories. It would be the same if someone asked to include "ultrabooks" as a separate item from laptops.
I would vote to adjust it to @patrickhlauke suggestion rather than keeping the current version.
from wcag.
@avkuo This change would need to be approved by the group, so Patrick creating a PR for the group to discuss is fine.
from wcag.
FWIW PR is now here #3776 for discussion
from wcag.
as said in #3776 (comment) let's make a swift decision either way on this one (either accept the PR and make the change, or close the PR and close the issue here just with a comment)
from wcag.
Related Issues (20)
- cred
- Hidden content in bi-lingual websites HOT 5
- htmk.forms.teixk
- WCAG 2.1 Techniques are 404ing HOT 3
- Clarification needed for 3.3.2 Understanding doc example bullet
- No definition of what constitutes an A, AA, or AAA conformance Level HOT 85
- Technique G65: Providing a breadcrumb trail (position). HOT 1
- 2.5.8 Target Size (minimum) "at least HOT 1
- 2.5.8 Understanding "draw" language HOT 10
- 2.5.8 Target Size overlapping content vs intersecting HOT 1
- Is providing a tooltip on hover sufficient for meeting 1.4.1: Use of Color? HOT 5
- Target size: "non-target text": interpretation HOT 11
- 1.2.1 Audio-only and Video-only - captions as alternative to audio - draft note for Understanding text
- Should there be a technique for 1.4.4 that mentions `rem` units? HOT 2
- https://canny.io/register?referral=drzwTt di
- orhanoguz356 HOT 1
- Accessible name link in Label in Name understanding document goes nowhere HOT 3
- SC 1.3.4 Orientation & restrictions of content and functionality
- WCAG 2.2 Understanding: Position of “In Brief“ sections HOT 8
- Understanding pages failing 1.4.10 HOT 5
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from wcag.