Participants
- Peter Mathis
- Philip Bauer
- Johannes Raggam
- Maik Derstappen
- Paras Chawla
Agenda
- Accessibility issues -> general accessibility improvements.
- Template movement status
- Timezone status?
- PLIPs status?
- collective.exportimport fix_html migration step.
Accessibility improvements
Hannes suggests making the template moves first in the packages before improving accessibility tasks.
Accessibility tools to check classic ui demo page for example:
- AXE
- Wave
Tools
ARC Toolkit - Page-Level Testing - TPGi — a Vispero company (There are Firefox and Chrome extensions for it)
https://wave.webaim.org/ (Also browser extensions)
https://www.deque.com/axe/ (Also with browser extensions)
collect ideas in a PLIP
Peter mentioned improvements on the Plone Dropdown menu in the latest Project. He implemented Keyboard navigation with TAB, Cursor and Space keys like defined in the WCAG standards.
Note: there is an old PLIP about Classic-UI accessibility: Accessibility fixes for Plone Classic · Issue #3383 · plone/Products.CMFPlone · GitHub we eventually should keep track of our ideas inside this plip… or create a new one …
Template movement
Peter will remotely join the Bucharest sprint (16th-20th March) and move templates around… and keep continuing at the Buschenschank.
Documentation:
Maik did 4 PRs for
- view: Replace Plone 5 links with Plone 6 links in views chapter by MrTango · Pull Request #2057 · plone/documentation · GitHub
- vocabularies: add vocabularies documentation by MrTango · Pull Request #2056 · plone/documentation · GitHub
- templates: add templates docs by MrTango · Pull Request #2055 · plone/documentation · GitHub
- annotations: add annotations documentation and examples by MrTango · Pull Request #2054 · plone/documentation · GitHub
Timezone
Backend is timezone aware already.
We need to have UI components to select timezone for event dates.
Maybe check package from Mikel: GitHub - collective/collective.datepickerpattern
Underlying issue for datetime picker: pat-datetime-picker relies on browser language configuration instead of Plone configuration · Issue #1328 · plone/mockup · GitHub
PLIP Status
everything is collected at Classic-UI Team · GitHub
We need to tag them properly if we’re working on them in sprints … bssp (Buschenschank) for example
collective.exportimport
Hannes wanted to add the “fix_html” code to “plone.app.upgrade” … maurits said its too late for that, also it's a potentially very long running upgrade step.
We agreed on adding a code recipe to the documentation at least to show how to use the view in a custom migration step