For a prototype, sure, accessibility might not be top of the list. But everything about the way this is advertised makes it sound like a production-ready product ('it's a stable, rock-solid product') and your FAQs are actively misleading people by implying that it produces accessible output.
It's also orders of magnitude harder to make an inaccessible product accessible than it is to build it in an accessible way in the first place
> Svija pages are fully-readable by screen readers, and you can add special text for each page in Svija Admin, visible only to screen readers.
I tested the accessibility with a keyboard and screen reader. With a keyboard, when you press the tab key, focus should usually go left-to-right, top-to-bottom. On this page the first link you tab to is 'Request Access'. From there the tab key goes backwards, to FAQ, Examples etc, then up to Vibe, Blazing Speed etc. Then it jumps down to the footer, does the same reverse order, then jumps all over the place.
The buttons in the main content to trigger animations aren't focussable at all, so aren't accessible without a mouse or touchscreen.
I explored the page with NVDA (a free screen reader) and found a number of sections and links where what was read out was different to what was shown in screen. It looks like you have a hidden HTML DOM that's exposed to screen readers and I assume this is out of sync somehow with what's on screen? I also got a bunch of links that didn't appear on the screen at all.
Exploring with the NVDA elements list (Insert+F7) shows a lot of junk in the Links list - links with text like 'id1584143858', 'UCmfF3YOMVyRcd0m-WpMUZ2g' etc. The Buttons list doesn't show the animation trigger buttons (because they're not marked up as buttons) and the Landmarks list is empty, meaning no easy way to jump to nav, header, footer etc.
Browser zoom is completely broken. The page looks the same at 500% zoom as it does at 100%.
Accessibility is important, and it's really disheartening when new page-building platforms like this pop up that clearly haven't been audited by an accessibility specialist or run past a disabled person who uses assisitve technology, especially when they specifically give the impression they're accessible as the FAQ answer does
I think OP means that new hires are receiving actual spearphishing emails from attackers outside of the company, not that they're testing them by sending fake spearphising emails. (I misread it as the latter at first too)
> Peanut butter is available now, but not that popular
I might be an outlier but my family eats peanut butter all the time, and you wouldn't have any trouble finding it even in small local shops. Peanut butter and j(elly|am) sandwiches are less popular but I maintain that they're America's greatest export.
DVLA systems seem to be an absolute mess, and many public-facing systems are still using the DirectGov styling (which was replaced by GOV.UK in 2012). A lot of their services are completely unavailable overnight from 7pm-7am. So if you sell a vehicle on the last day of the month and go to register the sale after 7pm, bad luck - you're getting charged another month of vehicle tax.
PaaS ran on AWS anyway, so it wouldn't be Amazon (I would guess? Unless they think they can charge more/upsell by departments procuring directly from them). Perhaps Google or MS were upset that by PaaS running atop AWS, AWS became the de facto 'official' cloud service for government?
> The computer would randomly wake up from hibernate and drain the battery till it was dead.
I had exactly the same thing on my XPS 15. I'd take it out of my bag, it'd be warm and the battery would be dead. Plus one day it suddenly decided it didn't have a TPM module (didn't even show up in BIOS) so BitLocker stopped working, and of late the CPU is constantly throtling and fans running at full blast because it's overheating even with next to no load (I've checked the fans for dust).
Hopefully this starts supporting accessibility tools before it gets too much traction and people start shipping inaccessible apps. The WebAssembley output demos on the homepage just render to a <canvas> and are completely inaccessible with any of the usual tools (screen reader, keyboard-only, voice dictation etc) but there's a GitHub issue (https://github.com/slint-ui/slint/issues/32) so fingers crossed.
Yeah, I keep coming back to Concrete5 (now Concrete CMS). We don't often do CMS-based projects but when we do I test out all the big names and Concrete wins out every time. It had a block-based page editor years before Wordpress introduced Gutenberg and theming has always been pretty straightforward.