Re: [WCAG2ICT] Google doc for 2.4.2 Page Titled

> On Oct 16, 2025, at 9:07 AM, Mary Jo Mueller <maryjom@us.ibm.com> wrote:
> 
> Hi all,
>  
> I copied in the original editor’s draft content (Proposal 0) which is only there for reference.
>  
> We have 3 variations of proposed updates for 2.4.2 Page Titled in the Google doc <https://docs.google.com/document/d/1qFOc8cip3tKbH35XsxwYpZXxycLMhVgblbabg5V4UCY/edit?usp=sharing>. Please review and give feedback during the week so we can hopefully reach consensus by the next meeting.
>  
> Gregg, you were also going to work on some alternate language for Orientation (for the example/note) that we didn’t get back to during the meeting. If you can send me that,  I can create a Google doc to compare changes/proposals in a single place.
>  
> Best regards,
>  
> Mary Jo Mueller
> IBM Accessibility Standards Program Manager 

Boy I  should not have let this wait.  I knew what to write when I said that - but then we had a meeting right after that we were late for.

Here is my best pass at it  
I ALSO FOUND I HAD TO FIX SOME FLAW IN OUR LOGIC.  
For example   it is not suffficient that the hardware not be re-orientatable since it could be displayed on two fixed displays each in a different orientation.  The key is that the DOCUMENT will not ever be displayed on in more that one orientation across all devices it might be displayed on) - NOT that it is displayed on fixed devices. 
  (changes shown are the changes from the version I  find at https://services.w3.org/htmldiff?doc1=https%3A%2F%2Fdeploy-preview-780--wcag2ict.netlify.app%2F%23orientation&doc2=https%3A%2F%2Fdeploy-preview-799--wcag2ict.netlify.app#orientation 


Applying SC 1.3.4 Orientation to Non-Web Documents

This applies directly as written, and as described in Intent from Understanding Success Criterion 1.3.4 .  <https://www.w3.org/WAI/WCAG22/Understanding/orientation#intent>, when the  except for non-web documents that will never be is displayed on hardware that is designed to be reoriented in more than one orientation in typical use.


Example (Added): Examples of non-web documents that will never be displayed in more than one orientation in typical use would be 1) a building directory that is only displayed on displays (of any type including iPads) that are all fixed to the wall in one orientation, 2) reports of results of a test that are displayed only on the screen of the testing device, and 3) the status report sent to the screen of a copy machine (but not the status report that would be sent to a web interface to the same machine). 

Applying SC 1.3.4 Orientation to Non-Web Software

 <https://services.w3.org/htmldiff?doc1=https%3A%2F%2Fdeploy-preview-780--wcag2ict.netlify.app%2F%23orientation&doc2=https%3A%2F%2Fdeploy-preview-799--wcag2ict.netlify.app#applying-sc-1-3-4-orientation-to-non-web-software>
This applies directly as written, and as described in Intent from Understanding Success Criterion 1.3.4 .  <https://www.w3.org/WAI/WCAG22/Understanding/orientation#intent>, when the  except for non-web software that will never be is displayed on hardware that is designed to be reoriented in more than one orientation in typical use

Example (Added): Examples of non-web software that will never be displayed in more than one orientation in typical use would be 1) software for a typical calculator that does not support screen re-orientation, 2) software menus and controls on a copier or other device that is not intended to be viewed in more than one orientation (but not any remote control software  or app for the same device that runs on computers or mobile devices) 3) software on a wristwatch that is not intended to be viewed when the watch is not on the wrist  4) special applications such as software for dislays around a building that will only be used on a known set of displays that are all permanently affixed in the same orientation. 

Note 2 (Added) (for non-web software)

See also the Comments on Closed Functionality  <https://services.w3.org/htmldiff?doc1=https%3A%2F%2Fdeploy-preview-780--wcag2ict.netlify.app%2F%23orientation&doc2=https%3A%2F%2Fdeploy-preview-799--wcag2ict.netlify.app#comments-on-closed-functionality>.