diff --git a/.github/workflows/push-actions.yml b/.github/workflows/push-actions.yml index 8174fabc..6ab5d60d 100644 --- a/.github/workflows/push-actions.yml +++ b/.github/workflows/push-actions.yml @@ -52,7 +52,7 @@ jobs: # https://mirror.cs.uchicago.edu/google-chrome/pool/main/g/google-chrome-stable/ run: | apt search '^google-chrome.*' \ - && wget -q -O /tmp/chrome.deb http://dl.google.com/linux/chrome/deb/pool/main/g/google-chrome-stable/google-chrome-stable_130.0.6723.58-1_amd64.deb \ + && wget -q -O /tmp/chrome.deb https://mirror.cs.uchicago.edu/google-chrome/pool/main/g/google-chrome-stable/google-chrome-stable_132.0.6834.110-1_amd64.deb \ && sudo apt install -y /tmp/chrome.deb --allow-downgrades \ && rm /tmp/chrome.deb - name: Log system details diff --git a/bin/checkHTML.sh b/bin/checkHTML.sh index 90f85252..7216100d 100755 --- a/bin/checkHTML.sh +++ b/bin/checkHTML.sh @@ -86,6 +86,12 @@ If that does not work, you may need to do a global update of @axe-core/cli: sudo npm update -g @axe-core/cli +******************************************************************************** +* NOTE: If you are seeing this message in GitHub Automated Tests, you need to +* update push-actions.yml to ensure the version of Chrome being downloaded there +* matches the one in your package.json +******************************************************************************** + ' 1>&2 exit 1; diff --git a/content/body/accessible-pdf-generation.php b/content/body/accessible-pdf-generation.php index 0a2ce852..c44c2c9c 100644 --- a/content/body/accessible-pdf-generation.php +++ b/content/body/accessible-pdf-generation.php @@ -324,13 +324,38 @@ function saveByteArray(reportName, byte) {

Feedback from a Screen Reader User

-

Vishnu Ramchandani, an experienced screen reader user, was kind enough to help us test the PDFs that we generated with Open HTML to PDF. He confirmed that he was able to read the information in the generated PDFs, but added some UX feedback to see if we can incorporate them in our PDF reports. Here is his feedback, along with what actions we took.

+

Vishnu Ramchandani, an experienced screen reader user, was kind enough to help us test the PDFs that we generated with Open HTML to PDF. Vishnu confirmed that the generated PDFs were accessible for screen reader users but provided valuable UX feedback to improve the user experience. Below is his feedback and the actions we took to address the issues:

+
    -
  1. Page title: To ensure consistency and clarity, the document title and the filename should both be same and should be meaningful. -
    2. -
  2. Reading behavior of lengthy paragraphs in tables: Screen reader users experience line breaks when reading lengthy paragraphs in table columns using arrow keys. A paragraph is read in a broken manner, making it hard to follow. It is best to ensure that lengthy paragraphs are presented in a linear, single-column format when possible. This helps screen readers read the content in a logical order without breaking lines. -
    3. -
  3. Issue with Splitting URLs/Links: A single URL or link splits into multiple lines, making screen reader users think there are multiple links instead of a single one. To prevent links from splitting across multiple lines, consider the following approaches: Use non-breaking spaces ( ) between words in the link text to prevent line breaks. Apply CSS to ensure the link text does not break into multiple lines. For example, using white-space: nowrap; can help keep the link text on a single line. -
    4. +
  4. Page Title Consistency +
    +
    Feedback:
    +
    The document title and filename should be consistent and meaningful to ensure clarity for users.
    +
    Action Taken:
    +
    We updated the title of the PDF to match the filename. This adjustment improves consistency and makes the document more user-friendly. When implementing your own solution, remember that this is not a default behavior in the Open HTML to PDF library and should be explicitly configured.
    +
    +
    5. +
  5. Reading Behavior of Lengthy Paragraphs in Tables + +
    +
    Feedback:
    +
    Screen readers encounter issues when lengthy paragraphs within table columns are broken into lines. This disrupts the reading flow, making it difficult for users to follow the content. To address this, lengthy paragraphs should ideally be displayed in a linear, single-column format.
    +
    Action Taken:
    +
    Unfortunately, this behavior seems to be a limitation of PDF technology. While we cannot fully resolve this issue, we recommend keeping table row text concise and avoiding lengthy paragraphs. If you are aware of any workaround to mitigate this issue, please share your insights with us, and we will update our recommendations accordingly.
    +
    +
    6. +
  6. Issues with Splitting URLs and Links + +
    +
    Feedback:
    +
    When URLs or links break across multiple lines in the PDF, screen readers interpret them as multiple links, leading to confusion. To prevent this: +
      +
    1. Use non-breaking spaces ( ) in link text to avoid line breaks.
      2. +
    2. Apply CSS styles such as white-space: nowrap; to keep links on a single line.
      3. +
    +
    +
    Action Taken:
    +
    This issue also appears to be a limitation inherent to PDF technology, as even advanced tools like Adobe InDesign exhibit this behavior. As a best practice, we recommend keeping link labels concise but descriptive to minimize splitting. If you have additional solutions or tools to address this, please reach out to us — we are eager to incorporate any new strategies.
    +
    +
- diff --git a/content/body/tooltip.php b/content/body/tooltip.php index 9a9921c6..245d8bb9 100644 --- a/content/body/tooltip.php +++ b/content/body/tooltip.php @@ -22,8 +22,6 @@ This solution can be styled exactly as wanted and uses the maximum value of a z-index in the document. We show different types of tooltips below, based on how they are triggered. It will disappear when keyboard users press the Escape key. - It doesn't work in mobile, which while consistent with other tooltip solutions, - is something that we are still looking to fix. If anyone has any ideas, please feel free to reach out to me on Twitter.

Clickable tooltip

@@ -39,21 +37,21 @@ Vehicle Inspection Form
-
-