AICTPO AI Coding Agents Knowledge Module
AICTPO AI Coding Agents FAQ — Knowledge Module
AICTPO AI Coding Agents knowledge module — UI selectors, data model, and page states documenting FAQ.
sidebutton install aictpo FAQ
Accordion section with 9 questions about the AI agents platform. The section anchors at #faq on the home page rather than living at its own URL.
Layout
The section heading appears above a vertical stack of 9 question rows. Each row collapses to a single line by default and expands inline when its trigger button is clicked. Rows are not mutually exclusive — the user can have several open simultaneously.
Interaction
Each question row is a button with aria-expanded toggling between "false" (collapsed) and "true" (expanded). The answer panel is the next sibling and is hidden via [hidden] or zero-height styling when collapsed. Clicking the button or pressing Enter / Space while focused toggles the state.
Selectors
| Element | Selector |
|---|---|
| Section root | section#faq, [data-section="faq"] |
| Question button | button[aria-expanded] (within the section) |
| Question label | the button's text content |
| Answer panel | element referenced by aria-controls |
| Active (open) state | button[aria-expanded="true"] |
Common tasks
Snapshot all questions: scroll #faq into view, list every button[aria-expanded] inside it, capture text content for each.
Read all answers: for each question button, click to expand if aria-expanded="false", snapshot the matching answer panel by aria-controls ID, then collapse.
Verify count and order: assert exactly 9 question rows and that the visible label text matches the expected question copy.
Gotchas
- The answer panels are inert when collapsed — they may not be in the accessibility tree at all, so a snapshot before expansion will miss them.
- Smooth-scroll on the parent page can intercept
#faqdeep links; wait for scroll to settle before reading positions. - The accordion is intentionally non-exclusive. Tests that assume "expanding question N collapses question N-1" will fail.
- Keyboard activation works on Enter and Space — both should be supported in any QA flow that exercises a11y.