Hii Ali Rana,
So, there is no ticket regarding the WCAG as of now, you can contact @Adam 
Monsen<mailto:[email protected]> , he's been reviewing my code for the 
fineract site improvements 
(https://issues.apache.org/jira/browse/FINERACT-2484). Currently we are working 
to migrate the fineract site from hand-maintained html pages to a static site 
generator workflow. You can find the migration plan in the attachment, and more 
details in the comments.
Feel free to dm if you need any help.


On 2026/02/21 17:20:07 Ali Rana wrote:
> Hello Apache Fineract Community,
>
> My name is Ali Mahmood Rana and I am a developer interested in contributing
> to Apache Fineract for Google Summer of Code 2026, specifically targeting
> FINERACT-2440 (Front End Application MVP).
>
> As an initial contribution, I have been working on the apache/fineract-site
> repository (fineract.apache.org) and identified multiple color contrast
> accessibility violations that do not meet WCAG 2.1 Level AA standards
> (minimum ratio of 4.5:1 for normal text, 3:1 for UI components and large
> text).
>
> --- What I Found ---
>
> Navigation / Sidebar:
> - Several navigation link and menu item text colors have insufficient
> contrast against their background colors, falling below the WCAG 4.5:1
> minimum threshold for normal text.
> - Active/hover state colors also fail to meet the required contrast ratios.
>
> Dashboard / Data Tables:
> - Table header text and secondary/muted text within table cells (such as
> labels and metadata) have contrast ratios below the WCAG minimum.
> - Some button text and icon colors within table rows also fail the 3:1
> minimum for UI components.
>
> --- My Approach ---
>
> I audited the website using Chrome DevTools Accessibility panel and the
> WebAIM Contrast Checker, identified the failing color values in the site's
> CSS/HTML source, and applied WCAG 2.1 AA-compliant adjustments while
> maintaining the existing visual design and style.
>
> --- Next Steps ---
>
> I have these fixes ready locally and am preparing to open a Pull Request on
> the apache/fineract-site repository. Before I do, I have a few questions
> for the community:
>
> 1. Is there an existing Jira ticket for accessibility or WCAG compliance on
> the fineract-site that I should reference in my PR?
> 2. Are there any specific CSS guidelines or design tokens in the site's
> codebase I should follow to ensure consistency?
> 3. Is there anything else the community would like me to address in the
> same PR while I am in this area of the codebase?
>
> Beyond this contribution, I am actively studying the Fineract Self-Service
> API to prepare a strong proposal for FINERACT-2440 (Front End Application
> MVP). I am experienced in JavaScript , TypeScript and React, and I am
> genuinely excited about building an accessible, user-facing customer portal
> on top of the Fineract API.
>
> Thank you for your time. I look forward to being part of this community.
>
> Best regards,
> Ali Mahmood Rana
> GitHub: https://github.com/AliRana30
> Email: [email protected]
>

Reply via email to