Developer Diary
  • Developer Diary
  • 2019

    • June 2019
    • July 2019
    • August 2019
    • September 2019
    • October 2019
    • November 2019
    • December, 2019
  • 2020

    • January 2020
    • February 2020
    • March 2020
    • April 2020
    • May, 2020
    • June 2020
    • July 2020
    • August 2020
    • September 2020
    • October 2020
    • November 2020
    • December 2020
  • 2021

    • January 2021
    • February 2021
    • February 2021
    • April 2021
    • May 2021
    • June 2021
    • July 2021
    • August 2021
    • September 2021
    • October 2021
    • November 2021
    • December 2021
  • 2022

    • January 2022
    • February 2022
    • March 2022
    • April 2022
    • May 2022
    • June 2022
    • July 2022
    • August 2022
    • September 2022
    • October 2022
    • November 2022
    • December 2022
  • 2023

    • January 2023
    • February 2023
    • March 2023
    • April 2023
    • May 2023
    • June 2023
    • July 2023
    • August 2023
    • September 2023
    • October 2023
    • November 2023
    • December 2023
  • 2024

    • January 2024
    • February 2024
    • March 2024
    • April 2024
    • May 2024
    • June 2024
    • July 2024
    • August, 2024
    • September 2024
    • October 2024
    • November 2024
    • December 2024
  • 2025

    • January 2025
    • February 2025
    • March 2025
    • April 2025
    • May 2025
    • June 2025
    • July 2025
    • August 2025
    • September 2025
    • October 2025
    • November 2025
    • December 2025
  • 2026

    • January 2026
    • February 2026

January 31, 2020

Accessibility task force check-in

Lupe check-in and discussions

TAP Peer review of M's work

MS MS Accessibility Insights Report

  • Do research on links that scroll, should they be hidden from accessibility things, or should they change focus.
    • actually, it looks like native HTML handles this well
  • Took a long time though.

It was our first time, and there was some figuring things out, but it took almost 2 hours.

So, I don't think this is either reserved for big reports like this, or we only use parts of the test. Some parts were irrelevant, and some I just passed because it asked you to do manual work that Axe will do for you.

Honestly, the keyboard section may be the only part that offers something other tools don't, namely, the walkthrough of how to determine if keyboard usage meets the success criterion.

PGP Flexbox product description issues

  • turned out it was just B, who made everything inside a particular div with the class "container" be a flex parent. Container is used everywhere though, so just using a child selector instead fixed the problem.

"View All Products on Channel Pages Taking Too Long"

When you arrive at this URL and it's loading slow, it's just a page with a featured items brick.

It does seem to me that the majority of the waiting is on the Server side, so I wonder if in certain environments Pimcore is not caching this list?

So there are few options.

  1. Have less featured items
  2. Build a "load more" for this brick
  3. Use the filter app instead that already has load more, but then E will need to build an API endpoint for things like this.

But I would want E to weight in before picking an approach. Maybe it's fixable some other way.

I'm fairly sure the issue isn't an image issue, it seems to load well after the server finally comes back with a page.