EVOLIZEDIGITAL RISK INTELLIGENCE

METHODOLOGY

How Evolize turns a public website into reproducible accessibility findings.

Evolize discovers and evaluates eligible public pages in a controlled browser environment. It combines deterministic rules, rendered-state analysis, interaction testing, and retained technical evidence to identify, consolidate, prioritize, and verify accessibility findings across the website.

Methodology version
v1.0
Current coverage
Accessibility
Evaluation mode
Automated public-site analysis
Last updated

Current evaluation scope

Evolize evaluates public-facing accessibility conditions across eligible pages and interface states that can be reached without authentication.

Evaluated at launch

  • Public URL discovery and page selection
  • Rendered document and accessibility-tree analysis
  • WCAG Level A and AA automated checks
  • Keyboard traversal and focus-behavior testing
  • Responsive layout and overflow evaluation
  • Form, instruction, validation, and error-state analysis
  • Dynamic interface-state evaluation
  • Evidence capture for affected elements and states
  • Consolidation across pages, templates, and shared components
  • Verification through subsequent scans

Evaluation boundaries

  • Publicly reachable pages and states
  • No authenticated or account-specific experiences unless explicitly supported
  • Results reflect the website state observed during the recorded scan
  • Some accessibility requirements still require expert or user-led assessment
  • Automated findings do not constitute complete WCAG certification
  • Findings do not determine legal liability or claim probability

The evaluation pipeline.

Each stage passes a defined output to the next stage.

Discover → Render → Evaluate → Capture → Consolidate → Prioritize → Verify

  1. Discover

    Evolize identifies eligible public URLs using available site signals, including sitemaps, robots directives, internal links, and submitted scan parameters. Pages are selected and grouped to reduce unnecessary evaluation of materially identical templates.

    OutputSelected pages and template groups

  2. Render

    Selected pages are loaded in a controlled browser environment so that client-rendered content, responsive behavior, and observable interface states can be evaluated.

    OutputRecorded browser states

  3. Evaluate

    Evolize applies deterministic accessibility rules alongside browser-based checks for keyboard operation, focus behavior, responsive overflow, and supported interaction states.

    OutputTechnical observations

  4. Capture

    Each detected issue is recorded with the affected page, element, selector, observed state, relevant technical context, and scan conditions. Where applicable, Evolize retains screenshot crops and accessibility-tree evidence.

    OutputReproducible evidence records

  5. Consolidate

    Repeated observations are grouped into actionable findings based on shared components, templates, technical causes, and evidence fingerprints. Evolize distinguishes isolated page issues from repeated and site-wide conditions.

    OutputConsolidated findings

  6. Prioritize

    Findings are prioritized using technical impact, affected reach, recurrence, user-flow context, evidence confidence, and remediation efficiency.

    Priority is an operational remediation signal. It is not a prediction of legal outcome.

    OutputRemediation order

  7. Verify

    Findings can be evaluated again after remediation. Evolize compares subsequent evidence with the original observation and records whether the issue remains open, has changed, or is no longer detected.

    OutputResolution status

What each finding contains.

Every Evolize finding connects the observed interface condition to the affected user experience, applicable technical requirement, remediation action, and verification state.

Visual evidence

Page
/pricing/
Viewport
390 × 844
State
Mobile navigation closed
Mobile navigation triggerbutton[data-menu-trigger]

Representative evidence · not a live scan

Observed technical state

<button class="menu-trigger">
  <svg aria-hidden="true">...</svg>
</button>

Detected stateNo accessible name was exposed for the interactive control.

Operational finding record

Interactive control has no accessible name

Rule impact
Serious
Affected reach
12 pages · shared header component
Remediation priority
High
Finding
Interactive control has no accessible name
Affected page
/pricing/
Affected element
Mobile navigation trigger
Stable selector
button[data-menu-trigger]
WCAG reference
4.1.2 Name, Role, Value
User impact
Screen-reader users may not understand the purpose of the control.
Recommended action
Provide an accessible name using visible text, aria-label, or aria-labelledby.
Verification status
Open

How remediation priority is assigned.

Evolize separates technical rule impact from operational remediation priority. Priority reflects how an organization should sequence corrective work, not the probability of litigation.

Technical impact
The seriousness of the underlying accessibility failure and its effect on access or operation.
Affected reach
The number of pages, templates, components, or interface instances affected by the same underlying condition.
Recurrence
Whether the condition is isolated, repeated, template-level, component-level, or site-wide.
User-flow context
Whether the issue appears within important navigation, conversion, account, support, or transaction paths.
Evidence confidence
The strength and reproducibility of the technical evidence supporting the finding.

RULE IMPACT + REACH + RECURRENCE + CONTEXT + EVIDENCE→ REMEDIATION PRIORITY

Limits of automated analysis.

Not legal advice

Evolize reports technical and behavioral observations. It does not provide legal advice or determine legal liability.

Not complete certification

Automated and browser-driven analysis does not constitute certification of complete WCAG conformance.

Human assessment remains necessary

Some accessibility requirements require expert review, assistive-technology testing, or evaluation by people with disabilities.

No guarantee of complete detection

A scan cannot guarantee that every accessibility barrier has been identified or that a legal claim will not occur.

Remediation priority indicates recommended work order. It is not a forecast of litigation probability or legal outcome.

Ruleset and methodology governance.

Every scan is associated with a defined methodology version, ruleset, and evaluation environment. This allows findings to be interpreted against the technical conditions under which they were produced and compared with subsequent scans.

Rules engine
axe-core 4.x with Evolize browser and evidence rules
Standards profile
Applicable WCAG Level A and AA criteria supported by the active automated ruleset
Browser environment
Chromium-based controlled browser environment
Responsive profiles
Desktop, tablet, and mobile evaluation profiles
Interaction coverage
Keyboard traversal, focus behavior, supported state transitions, validation states, and responsive behavior
Evidence model
Screenshot evidence, element metadata, stable selectors, accessibility-tree context, and scan-condition metadata
Consolidation model
Shared cause, component, template, selector, and evidence-fingerprint grouping
Verification protocol
Comparison of subsequent evidence against the original finding state

Results reflect the public website states observed during the recorded scan under the applicable browser, viewport, interaction, and ruleset conditions.

Change control

v1.0

Material changes to rules, evaluation behavior, consolidation logic, prioritization, or verification are recorded through methodology version updates. Reports retain the methodology version applicable at the time of the scan.

See the methodology applied to a public website.

Run an Evolize scan to review the pages inspected, evidence captured, findings consolidated, and remediation priorities identified.

RUN THE SCANVIEW SAMPLE REPORT