Hii Ali, continuing our yesterday's disucssion. I have raised the migration PR (https://github.com/apache/fineract-site/pull/53) Also added the respective comments in (https://issues.apache.org/jira/browse/FINERACT-2484) I will wait for Adam's reply on how to proceed from here, meanwhile you can go through the migration branch, also if you want you can contribute in making the UI pixel perfect. After migration there are some UI sections which were not preserved 100%, there are some minor changes, so u can work on that, you will get the current UI in (https://fineract.apache.org/). We will be working to make the site 100% template based, so if you find some segments which can be transformed from hand code , then you can do that too. Thanks.
On 2026/02/21 19:27:16 Ali Rana wrote: > This is really helpful! > > I would be very happy to collaborate on this. Your suggestion makes perfect > sense — once you share the migration branch, I can review the style > changes, fix the broken styles caused by removing inline CSS, and layer my > WCAG contrast fixes on top of that. A merged PR branch for the final > migration sounds like a clean approach. > > I will wait for you to share the branch tomorrow and will review it > carefully before making any changes. > > In the meantime, I will reach out to Adam Monsen today to introduce myself > and get his guidance on the WCAG changes before proceeding, as you > suggested. > > On Sun, 22 Feb 2026 at 00:02, Aira Jena <[email protected]> wrote: > > > Regarding the quick questions. > > Final call will be taken by Adam only regarding the WCAG changes. > > Regarding the migration, I have completed the initial migration of the > > site, but there is a blocker, after migration the styles got bit changed as > > we are no longer supporting inline css in index.html. That being said, if > > you would like then I will push my migration changes to a branch and you > > could help to fix the styles and then we can make a merged PR's > > branch(release branch) for final migration. After Adam's review and > > feedback we can finally integrate the migrations. Now this is purely my > > suggestion, migration and integration call will be taken by Adam. So please > > consult him before proceeding, by tomorrow I will share the initial > > migration branch so you get an idea how the changed project looks like and > > understand the changes. > > > > On 2026/02/21 18:46:19 Ali Rana wrote: > > > Hi Aira, > > > > > > Thank you so much for this — this is really helpful! > > > > > > I will check FINERACT-2484 right away to understand the migration plan > > > before opening my PR, so that my contrast fixes target the correct files > > in > > > the new static site generator workflow rather than the old > > hand-maintained > > > HTML. > > > > > > I have also submitted a Jira account request and will reach out to Adam > > > Monsen once my account is activated to coordinate the WCAG fixes with the > > > ongoing site improvements. > > > > > > A quick question: given that the site is being migrated to a static site > > > generator, would it be better for me to: > > > a) Apply my contrast fixes to the current HTML files now, or > > > b) Wait and apply them directly in the new static site generator > > templates? > > > > > > I want to make sure my contribution lands in the right place and does not > > > create extra work for the migration. Happy to DM you as well if easier. > > > > > > Best regards, > > > Ali Mahmood Rana > > > > > > On Sat, 21 Feb 2026 at 23:07, Aira Jena <[email protected]> wrote: > > > > > > > Hii Ali Rana, > > > > So, there is no ticket regarding the WCAG as of now, you can contact > > @Adam > > > > Monsen <[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] > > > > > > > > > > > > > > >
