✅ Questions and Answers submitted for Milestone 2 a/b

General

Q: Can we see the list of issues raised in 1a/b?

A: This milestone is currently running, we don’t have the result yet.

Q: Can we see the Test Protocols from 1a?

A: This milestone is currently in progress, so we do not have the final results yet. The results are not publicly available at this time. However, you can request a draft version of the report from us.

Q: We have access to all required hardware/software listed in the minimum matrix but it would be nice to have a little bit more insight.

A: We haven’t used a specific setup for the tests.

Q: Visual design scope: Our understanding is that Milestones 2a and 2b are focused on establishing the accessible design system and improving the accessibility, consistency and reusability of Joomla’s UI components, rather than undertaking a broader redesign of Joomla’s visual look and feel. Could OSM confirm that this is the intended scope?

A: Yes, that is the scope.

Q: Scope of the core component set in Milestone 2a: The RFP gives buttons, form controls and non-sortable data tables as examples of the core component set, with the final selection informed by Milestone 1b. To help us scope and price the milestone appropriately, does OSM have an approximate number or range of core component types that bidders should plan for in Milestone 2a? We understand that the exact set may be refined once the Milestone 1b remediation plan is available.

A: Unfortunately, we don’t have a fixed number. Your proposal may include scoping, such as a list of components, a number of components, or a number of hours to spend on this deliverable.

Milestone 2a

Deliverable 1: Design Tokens

Q: Do you have an existing naming scheme or style guide for token names, or would we be producing one?

A: We currently have an inconsistent scheme. One of the tasks will be to develop a consistent scheme while respecting the existing one, so that no existing elements need to be changed.

Deliverable 2: Core Accessible UI Components

Q: Are we defining tokens and building semantic code for reference, or are we working with the dev team to incorporate these tokens and components into existing tech stack?

A: You will be working within an existing technology stack and codebase. Collaboration with the development team is therefore both necessary and expected.

Q: Are there any requests for technologies to use in the components?

A: HTML, PHP, CSS, and JavaScript are the core technologies used by Joomla!.

Q: Meaning, can we supply them as Web Components for example?

A: Depends on the situation. When it makes sense then Web Components are allowed.

Q: What are the requirements for browser support?

A: See the "RFP - MS1a Expert Audit - Scope Clarification (Addendum)" - Browser Matrix

Deliverable 3: Component Documentation and Examples

Q: Is there a documentation system in place?

A: For some of our documentation, we currently use Docusaurus. In general, we prefer open-source tools, but we are open to suggestions and would be happy to consider alternative solutions as part of the proposal.

Deliverable 5: Validation Against MS1a Test Protocols

Q: Is there a framework for documenting component audit results? Are we free to devise one ourselves?

A: In Milestone 1a we have used CAAT (https://www.caat.report/). You don’t have to use CAAT but we want a comparable report to the one we have for 1a.

Milestone 2b

Deliverable 1: Complex Accessible UI Components

Q: Will there be any changes in the requested complex component set?

A: This is possible, depending on the results of Milestone 2a.

Q: Should we budget for the eight listed, or account for additional components?

A: You should budget for the eight listed items as a minimum. Unfortunately, we cannot provide any further guidance on how to calculate the budget.

Deliverable 3: Stable Versioned Package on GitHub

Q: This goes for 2a D4 as well: are there any preferences for commit message style (such as conventional commits)?

A: No, it should follow industry standards and a message should be a description of the change.

Deliverable 4: Guided-Tour Readiness

Q: Is there any documentation on the requirements for this?

A: Yes, we have documentation for Guided Tours:

The core requirement is that the elements can be targeted and focused.

Projects