What AI Accuracy Percentages Really Mean

Accuracy is the fraction of evaluated cases the system labeled correctly. If a test contains 100 cases and 95 are correct, the measured accuracy is 95 percent for that test. The number does not say which five cases were wrong, whether all errors have equal impact, or whether the test resembles future inputs. A dataset with many easy or common cases can make accuracy appear high while performance on an important rare case remains poor. Ask how the evaluation set was constructed and kept separate from training and tuning. A model can memorize examples or benefit from repeated adjustments to a benchmark. A held-out test set gives a more credible estimate, but it still needs to represent the deployment population and task. Data leakage, duplicated records, outdated samples, or a narrow collection method can make results misleading. Look beyond accuracy to the confusion matrix. Precision describes how many predicted positives were correct; recall describes how many actual positives were found. Specificity and false-positive rates help describe negative cases. Which measure matters most depends on the consequences. A spam filter can tolerate some messages sent to review; a high-stakes medical screening system requires careful follow-up and should not treat a positive result as a diagnosis. Performance can differ across language, age, lighting, device, region, or other relevant subgroups. An overall average may hide those differences. Request results by meaningful group, with sample sizes and uncertainty, and consider whether the evaluation process had enough examples to support each estimate. If the system changes or the environment shifts, old results may no longer describe present performance. An accuracy claim is useful when it is specific: the task, dataset, date, threshold, and error measures are clear. It is not a guarantee about any individual output.