Skip to content

1.3.4 Orientation - update Note 1 to remove info about having a sensor #780

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.

Sign up for GitHub

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

Jump to bottom
Open
wants to merge 11 commits into
base: main
Choose a base branch
from
Open

1.3.4 Orientation - update Note 1 to remove info about having a sensor #780

wants to merge 11 commits into from

Conversation

maryjom
Copy link
Contributor

@maryjom maryjom commented Sep 12, 2025 •
edited
Loading

Per Issues #779 and #787 and alignment with the latest EN 301 549 proposed updates:

  • Split guidance between a non-web document and non-web software section
  • Remove "or that has no sensor to detect or change the orientation" from Note 1.
  • Add in note for the example of a non-web document from the EN 301 549 10.1.3.4 section.
  • Add in precondition rather than use "essential exception".

@maryjom
1.3.4 Orientation - update Note 1 to remove info about having a sensor
6c115af 
Per Issue #779 for alignment with the latest EN 301 549 draft:
- Remove "or that has no sensor to detect or change the orientation" from Note 1.
- Make note 1 only apply to non-web software - not non-web documents.
@netlify Netlify
Copy link

netlify bot commented Sep 12, 2025 •
edited
Loading

✅ Deploy Preview for wcag2ict ready!

Name Link
🔨 Latest commit 2e32dbb
🔍 Latest deploy log https://app.netlify.com/projects/wcag2ict/deploys/68dec9bb10f021000819fe26
😎 Deploy Preview https://deploy-preview-780--wcag2ict.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

bruce-usab
bruce-usab requested changes Sep 18, 2025
View reviewed changes
Copy link
Contributor

@bruce-usab bruce-usab left a comment

Choose a reason for hiding this comment

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

I strongly prefer our current wording. Lack of hardware support seems like the device just doesn't meet the requirement.

@bruce-usab bruce-usab self-requested a review September 18, 2025 14:16
bruce-usab
bruce-usab previously approved these changes Sep 18, 2025
View reviewed changes
Copy link
Contributor

@bruce-usab bruce-usab left a comment •
edited
Loading

Choose a reason for hiding this comment

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

Apologies, I was confused about the proposed changed. I think it's a good edit to drop reference to a sensor.

1.3.4 for PR780 diff

@maryjom
Change non-web software scoping to devices supporting content display…
4280802 
…ed in different orientations

This change tries to incorporate the essence/intent of what Gregg proposed in the 18 September meeting which was:

"this SC applies to non-web software if it is limited to only 'non-web software that is intended to be run on devices that supports software in more than one orientation"
maryjom
maryjom commented Sep 24, 2025
View reviewed changes
@maryjom
Add the same note to non-web document section
2a8886e 
The same essential exception also applies to non-web documents displayed on fixed-in-place displays.
maryjom
maryjom commented Sep 24, 2025
View reviewed changes
@maryjom
Copy link
Contributor Author

maryjom commented Sep 25, 2025

The latest V19 draft of the EN 301 549 received on Monday, 22 Sept. has the following notes and examples for non-web software:

NOTE: Non-web software that is only used on hardware that supports a single display orientation, or where it is an application that is run only on hardware that is physically fixed in one orientation (e.g. a building directory) is covered under the essential exception and therefore does not need to provide support for orientation changes.

EXAMPLES: Calculators and watches would not be expected to support two orientations.  Nor would building directory software written to ONLY be used on tablet devices bolted to the wall, all in the same orientation, be expected to support two orientations.

Is this OK as-is or are adjustments needed? If this language is preferable to what is currently in the PR, I can update the PR to match.

maryjom
maryjom commented Sep 25, 2025
View reviewed changes
maryjom
maryjom commented Sep 25, 2025
View reviewed changes
maryjom
maryjom commented Sep 25, 2025
View reviewed changes
@maryjom maryjom mentioned this pull request Sep 30, 2025
Open
maryjom
maryjom commented Sep 30, 2025
View reviewed changes
@bruce-usab bruce-usab linked an issue Oct 2, 2025 that may be closed by this pull request
SC 1.3.4 is problematic for some content appearing only on stationary hardware #787
Open
@bruce-usab bruce-usab mentioned this pull request Oct 2, 2025
Open
@bruce-usab bruce-usab linked an issue Oct 2, 2025 that may be closed by this pull request
1.3.4 - Consider removing "or that has no sensor to detect or change the orientation" from Note 1 #779
Open
bruce-usab
bruce-usab previously approved these changes Oct 2, 2025
View reviewed changes
Copy link
Contributor

@bruce-usab bruce-usab left a comment •
edited
Loading

Choose a reason for hiding this comment

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

Looks good to me. Diff preview

@maryjom
Incorporate the latest EN 301 549 updates
8b5093d 
This changes the precondition, note and examples for 1.3.4 Orientation to match what is in the latest EN 301 549.
maryjom
maryjom commented Oct 2, 2025
View reviewed changes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@bruce-usab bruce-usab bruce-usab left review comments

At least 1 approving review is required to merge this pull request.

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
2 participants
@maryjom @bruce-usab